In case you are processing and working with geospatial data on MySQL, you may be interested in the following UDF (plugin) for MySQL 5.1: Koji Okumura from Oki Labs Japan has ported two functions from PostGIS into a MySQL UDF:
In case you are processing and working with geospatial data on MySQL, you may be interested in the following UDF (plugin) for MySQL 5.1: Koji Okumura from Oki Labs Japan has ported two functions from PostGIS into a MySQL UDF:
If you have a database related blog and would like to add it to the relationalnews.com website for syndication, please post a comment or email your feed to contact@relationalnews.com.
Description:
The drupal_lookup_path function unnecessarily counts all rows of
the url_alias table to determine if any aliases are defined. This
can be expensive on a transactional database such as MySQL with
the InnoDB Storage Engine or PostgreSQL when a website has a lot
of aliases. This patch modifies the query to always only return
one row, possible because any existing pid will be greater than
0. If no aliases are defined, it will return 0.
Status:
This patch has not been merged into any release of Drupal.
Patch
This month’s (September 2008) edition of Linux Journal has an in-depth review of Zmanda Recovery Manager for MySQL (written by Alolita Sharma a veteran of Open Source). Oh, and we made it on the cover as well! If you are browsing Magazines section of your local bookstore, do look us up..
This is the 114th edition of Log Buffer, the weekly review of database blogs.
I am sorry to say that this log buffer was supposed to be edited by Dave Edwards, but he’s suffering from severe and long-lasting tooth pain and until his root canal is done he’s KO’d by a killer combo of painkillers and the pain that the painkillers can’t kill. I’ve been there myself, twice, and here’s a tip Dave. It hurts until the dentist takes out the needle. Then the pain goes away while he digs. The pain comes back that night. The next morning it’s worse than ever, unbelievably, writhingly bad. But later that afternoon, blisssssssssssss. :-) Good luck man.
This Log Buffer has been generated in a completely automated way with the help of the incredibly awesome AideRSS.
To give you an idea …
[Read more]Smithy commented on my blog post about the rumor of Monty leaving Sun with a pointer to an article on ComputerWorld Finland that mentions:
Widenius told to Computerworld Finland on Friday that negotiations are still on.
Meanwhile, Matt Asay, who seems to think Monty actually has left Sun (even though all other reports have been clear to mention that this is unconfirmed), writes of a new investment Monty has made.
Last week I speculated about the impact of Monty leaving Sun. In the end, if he does stay, it’s wonderful for Sun. If he leaves, he will no …
[Read more]Scenario: Someone wants to know which of the over 50 MySQL users have certain privileges.
There are many ways to solve this problem. Some of these scenarios are tedious and repetitious, others take no time at all.
The issue, of course, lies in what the “certain” privileges are. If it is “who has the SUPER privilege?” then a simple
SELECT user,host FROM mysql.user WHERE Super_priv='Y';
is sufficient. If it is “who has write access to the foo database”, you might write:
SELECT user,host FROM db WHERE Db='foo' AND Select_priv='Y';
but that only shows who explicitly has read permissions on that
database; it does not include those who have global read
permissions. The full query would be:
(more…)
|
MySQL 5.1 is almost ready for prime time, but in the meantime some brave users have already started putting it to work in production environment. MySQL wants to hear from these intrepid souls. The MySQL 5.1 use Case competition is under way. We want feedback from users who have found a practical usage for 5.1 features, and also from the ones who have met usability challenges. |
Two articles have already been published from the competition submissions. One …
[Read more]
For example, after executing this code:
create table t1 (id int, c char(10), d date);
insert into t1 values (1, 'abc', '2008-01-01');
insert into t1 values (2, 'def', '2008-08-19');
insert into t1 values (3, 'ghi', current_date());
select * from t1; …[Read more]