Comments on: MySQL Pays attention to Bugs (Finally!) http://www.mysqlperformanceblog.com/2009/05/20/mysql-pays-attention-to-bugs-finally/ Everything about MySQL Performance Sat, 21 Nov 2009 05:23:57 -0800 http://wordpress.org/?v=2.8.4 hourly 1 By: peter http://www.mysqlperformanceblog.com/2009/05/20/mysql-pays-attention-to-bugs-finally/comment-page-1/#comment-564670 peter Thu, 21 May 2009 18:42:11 +0000 http://www.mysqlperformanceblog.com/?p=691#comment-564670 Hehe, The "big features" is probably a wrong word here. I just think recent years a lot of work was done trying to move up market for enterprise database adding views, triggers, stored procedures etc which is what MySQL "core" market did not need so much. At the same point stability, performance, usability, operations tasks were not taken care of and these new features often were not well designed and integrated with other things. For example there is Replication since MySQL 3.23 but there is still not out of the box ways to check master is in sync with slave or resync them (maatkit or Google patches have solution for these). Debugging and profiling stored procedures is another example. Hehe,

The “big features” is probably a wrong word here. I just think recent years a lot of work was done trying to move up market for enterprise database adding views, triggers, stored procedures etc which is what MySQL “core” market did not need so much.
At the same point stability, performance, usability, operations tasks were not taken care of and these new features often were not well designed and integrated with other things.

For example there is Replication since MySQL 3.23 but there is still not out of the box ways to check master is in sync with slave or resync them (maatkit or Google patches have solution for these). Debugging and profiling stored procedures is another example.

]]> By: g http://www.mysqlperformanceblog.com/2009/05/20/mysql-pays-attention-to-bugs-finally/comment-page-1/#comment-564661 g Thu, 21 May 2009 13:39:35 +0000 http://www.mysqlperformanceblog.com/?p=691#comment-564661 Well your request 'we do not need more big features' will most likely be met, now that Oracle are in charge. Well your request ‘we do not need more big features’ will most likely be met, now that Oracle are in charge.

]]> By: idont http://www.mysqlperformanceblog.com/2009/05/20/mysql-pays-attention-to-bugs-finally/comment-page-1/#comment-564648 idont Thu, 21 May 2009 12:51:27 +0000 http://www.mysqlperformanceblog.com/?p=691#comment-564648 At my company we have a default, we push only stable releases to PROD... So, as you said, let's hope that the bug handling will radically change, because if you see how this nasty bug (http://bugs.mysql.com/bug.php?id=14194) has been fixed ("This bug cannot be fixed in 5.0, as 5.0 is now stable. Will be fixed in 5.1."), it is not acceptable. This bug is a catastrophy for many latin languages... This bug has been corrected in 2006 but was still not commited in a stable release at the end of 2008... What a shame... At my company we have a default, we push only stable releases to PROD…

So, as you said, let’s hope that the bug handling will radically change, because if you see how this nasty bug (http://bugs.mysql.com/bug.php?id=14194) has been fixed (”This bug cannot be fixed in 5.0, as 5.0 is now stable. Will be fixed in 5.1.”), it is not acceptable. This bug is a catastrophy for many latin languages…

This bug has been corrected in 2006 but was still not commited in a stable release at the end of 2008… What a shame…

]]> By: Ewen http://www.mysqlperformanceblog.com/2009/05/20/mysql-pays-attention-to-bugs-finally/comment-page-1/#comment-564542 Ewen Thu, 21 May 2009 07:43:34 +0000 http://www.mysqlperformanceblog.com/?p=691#comment-564542 Sergei, Fixed link. Thanks Sergei,

Fixed link.

Thanks

]]> By: Sergei Golubchik http://www.mysqlperformanceblog.com/2009/05/20/mysql-pays-attention-to-bugs-finally/comment-page-1/#comment-564528 Sergei Golubchik Thu, 21 May 2009 05:28:55 +0000 http://www.mysqlperformanceblog.com/?p=691#comment-564528 fix the url, remove &edit=2 from it :) fix the url, remove &edit=2 from it :)

]]>