Excellent explanation about the (infamous) issue:
It‘s been a long time, from my point of view, since MySQL was out with something exciting.
Since version 5.0 back in 2005 we mainly saw bug fixes. Version 6.0 is in development for years and I am not sure if it heads anywhere
(see the following post). So the following new article from MySQL was very encouraging.
I got the following question from one of our customers.
”I have a question regarding mysqldump.
I am using the following scenario:
Replication: one master and one slave, default engine is InnoDB.
If I execute musqldump (on slave) with --single-transaction option (for InnoDB) do I have to stop the replication on slave or it does not metter?
I guess that since the acquisition of Sun, and as result MySQL AB, by Oracle every MySQL user had wonder if Oracle is a good hosting place to Open Source like MySQL. Basically I am optimistic regarding the future of MySQL, but I think the community should stay alert and make sure Oracle know how match we care for MySQL. So I am attaching a link to a post by Michael "Monty" Widenius, the creator of MySQL where he states his fears regarding the upcoming for MySQL and ask your support.
I wish to embed MySQL database in a .NET SW. MySQL have a embedded product, but it is a C++ library, which really don't want to use directly. Does any one know of a .NET library, or even a managed C++ wrapper for this API I can use?
Does anyone know what is the default number of threads in MySQL?
Some tips for kill and showprocess list commands.