I won an iPod at php|tek. Since Apple does not support Vorbis Ogg my options were either to install some third party firmware or to sell the iPod. I went with option #3 and gave it to a friend of mine who is moving to South Africa for an internship that will have him traveling a fair bit. Since he is still using mp3 he got it as a farewell present. Now other friends have noted an interest in iPods as well. Since apparently outside of IT iPods giveaways are less common I will try to get each of them an iPod with my awesome computing skills (Ok, I won the first one with drinking alcohol, but I still have not really acquired the taste for drinking so ..).
Anyways the purpose of this post is to highlight some issues in MySQL that will hopefully get fixed in the 5.1 release cycle. And thereby I hope to enter their iPod Nano contest. Actually while I was browsing the changelogs I found that one issue I reported long ago has been fixed. Though they chose to fix a duplicate bug that was filed after my original post. You guys are hurting my feelings! ;-)
Another issue I found a while ago and filed a bug. Its about one of the new SQL Modes added that should prevent users from adding invalid dates called "ALLOW_INVALID_DATES". However this setting can be overritten by users which makes it impossible for a DBA to rely on the data being well formed. Until this is solved PostgreSQL can continue to mock MySQL on this point (though unfortunately there are still other issues they can then simply move to .. until those are fixed as well .. proper Foreign Key support comes to mind ..).
Another issue that I still need to confirm if more recent MySQL 5.1 builds have fixed is related to loading large SQL dump files. I ran into this one while trying out one of the sakila dumps. However I currently do not have MySQL 5.1 installed.
Actually I need to figure out how to run multiple MySQL versions on my windows machine. I have not been testing recent MDB2 releases with MySQL 4.0.x and lower which caused a bug to slip by in a recent release (but fixed now) that caused prepared statements to not fall back to emulation on older MySQL versions. Maybe I should just do the necessary steps on my VMWare Linux instance according to Kristians guidelines.
Anyways, I will be back with some more issues if I am able to uncover anymore. I will also try to confirm which of my other open bug reports is not yet fixed in 5.1 as well as poking the new features like Events, improved XML support and Partitioning. However I will hold off until 5.1.10 is released.
Wegen MySQL:
http://dev.mysql.com/doc/refman/5.0/en/multiple-windows-servers.html
Jeder Instanz braucht eine eigene my.cnf, das war's schon. Geht ueberigens auf Windows und auch auf *nix.
Uebrigens, wg. Kommentaren:
1) Hab im Feedreader auf den Beitrag geklickt
2) Dann das CAPTCHA geloest
3) Und dann war ich auf der Startseite
(Musste dann auf "read on", und runterscrollen, um hier etwas zu tippen.)
