MySQL Readies Release Candidate For 5.1
Anonymous Dolphin writes "MySQL has released plans for a final RC for the MySQL 5.1 server. Monty Widenius, the CTO and founder of MySQL, has put up a request for more feedback from the community. You can get the latest RC here. Please help with the testing of 5.1 and report your bugs here."
Whenever I read about a new MySQL version, I think about all of the hosting out there that are still running 4.x. I understand that you can't simply upgrade to the latest version as it would mess up customers' applications, but how about offering customers different versions of MySQL? Is it really that hard to do? A growing collection of well designed web applications require MySQL 5.x and it sucks to miss out om them simply because your hosting provider isn't database flexible enough.
First release with native XML functions. If there's indexing behind some of the XPath, this could be a very interesting release indeed.
I'd definitely be interested to hear what it's also missing that more XML aware databases include, though.
Tweet, tweet.
It was interesting to see Sun's reaction.
Apparently, MySQL AB (prior to purchase) were the ones contemplating making the move to more proprietary tools. It was set in motion and left on the table, then Sun purchased them.
Sun basically said "We have no need to put this in play, we don't make our money from a single product like MySQL AB did .."
A lot of people Criticized Sun for the idea, however the idea was the brainstorm of MySQL AB, not Sun.
I would like to use MySQL instead of Postgres - it's easier for me to install, maintain, and just plain understand. I don't like how PG does things a lot of the time and find it needlessly complex. But because MySQL lacks the seemingly basic ability to store a timestamp with better than second accuracy, I can't, because I have to store log events which are often more than one a second - much more - and I need to know exactly when. Milliseconds would be fine, microseconds would be great.
MySQL currently recommends some ridiculous hack where you strip the sub-second information from the time you send it and store it in another column, then write some kind of view which combines them back. What? I am not doing that to implement what I consider to be basic functionality! Do you remember how my motivation for switching is because I want things to be simple? Writing weird multi-column time recombination hacks is not my idea of simple.
Replication improvements, XML parsing, great features all - but please just give us timestamps with accuracy better than a second? A lot can and does happen in less than a second and I need to be able to log it with accuracy!
Let my new 7-digit UID be a lesson to all - write down your passwords.
The only thing that I look forward to in 5.1 is the addition of triggers for non-root users. I've fought many a battles with hosting providers wanting to charge me upwards of $120/hr to put my triggers in place as root because MySQL didn't allow regular users to run it.
Now, finding a hosting service willing to upgrade to 5.1 within a year after it's released is going to be a new bat
Change is inevitable, except from a vending machine -- Robert C. Gallagher
How about we fix the obvious too? This bug makes it impossible to have an Insert trigger and an update trigger both updating a table. Trying to do so triggers database duplicate keys because there isn't a good lock on the auto-inc value.
A bug, marked as serious and yet left pending since Feb'07 !
"Official" one from Feb 2005:
http://bugs.mysql.com/bug.php?id=8523
And here's another one going back to Nov 2003, which was strangely marked as a dupe of the above:
http://bugs.mysql.com/bug.php?id=1764
Should have put those in the original comment; apologies for my laziness.
Let my new 7-digit UID be a lesson to all - write down your passwords.
Also your view of MySQL is a couple years old. MySQL has made leaps and bounds on Postgres. Now that mysql has things like PL/SQL and Foreign Keys the differences between it and postgres have dwindled.
Disclaimer: I have a strong Oracle, Postgres, and MySQL background. I find them all to be excellent tools.