In MySQL 5.0 mainly error control was improved, such as strict mode was added to change famous MySQL behavior of cutting too large strings, too big numbers and allowing you to use dates such as February 31st.
In one case however reverse change was done - in regards to storage engine initialization. Previously if you start MySQL and Innodb storage engine fails to initialize (ie you resized log file but forgot to delete old ones) MySQL Server simply would not start. In recent MySQL 5.0 series however it will continue loading and simply have Innodb storage engine disabled.
This can cause numerous problems especially if you got use to old behavior and do not check MySQL logs but simply check it is started. It especially hurts if you have only some tables in Innodb so you might not notice part of your application does not function. Also monitoring often monitors MySQL is up and running and will not query all tables are accessible not …
[Read more]