A long standing bugAmong the many outstanding bugs for MySQL,
there is one that has sparked a fierce discussion, not only in
the bug report itself, but also in blogs, forums, mailing
lists.
Bug #19027: MySQL 5.0 starts even with Fatal InnoDB
errors was neglected for long time, until finally it got
fixed, and it is available in MySQL 5.1.36.
First off, what is it about?
In short, if an engine doesn't initialize correctly, the MySQL
server starts anyway, without the offending engine. Depending on
how you use the failing engine, this could be either a minor
annoyance or a complete disaster.
Annoyance: ARCHIVE fails to initialize, and you create
tables with the default engine (usually MyISAM), and after a
while you realize that the disk is filling up faster than you
expected. You will find out eventually.
Disaster: ARCHIVE fails to …
I've been on vacation this week, and decided to fine-tune some
old QA code. Opened the manual to see the syntax for a select
statement, and afterwards added to my random select generator the
following:
- all index hints (force, use, ignore, for join, for order by, for group by)
- lock in share mode, for update
- key_block_size for individual indexes
- hash, btree, rtree for individual indexes
- unique, fulltext, spatial for indexes
Especially important is the 'lock in share mode' addition. The
reason is InnoDB
has many serious bugs with this locking mode (insert ... select,
and others) in read committed mode.
So, I don't need multitable delete or update to reproduce those
bugs, since I can just do a simple select locking in share mode.
For example, the following bugs previously went without proper
testcase until I discovered this:
…
As others wrote, or as you can read on php.net or in my
twitter feed we've released the second, long awaited, release
candidate of PHP 5.3.0.
5.3 is rather big release including support for namespaces, closures, phar archives, internatioalization support via the new intl extension, improved SQLite support, mysqlnd as backend for the MySQL exensions, impressive performance improvements, ... and tons of other bigger and minor things.
Even though this server is running 5.3 already it's not suggested to be used in production evironments, yet but I'd really like to encourage everybody to test it and give feedback! I'm also interested in positive feedback, not …
[Read more]|
If you liked the article on QA before releasing, you may want to mark your calendars for this session at the MySQL Users Conference and Expo 2009, where Omer BarNir and Trim Pershad will tell everything about Software Quality and Testing in MySQL. Trim and Omer are veteran QA engineers, whose main goal is to improve the quality of MySQL products. Their session will tell you how the QA process evolved and what is going on right now. |
This task involves QA engineers, Build engineers, the Maintenance team, with help and cooperation from …
[Read more]This task involves QA engineers, Build engineers, the Maintenance team, with help and cooperation from …
[Read more]This task involves QA engineers, Build engineers, the Maintenance team, with help and cooperation from …
[Read more]|
|
I am glad to host in these pages a post by Philip Stoev, a remarkable QA engineer, creative, resourceful, and a notorious troublemaker. I met Philip by email in 2007, when I was exploring his Perl modules, which I used for one of my most rewarding articles. A few months later, when we met in person during the MySQL Developers Meeting, Philip was hired as a QA engineers, with my warmest recommendations. This post is about the … |
As promised we are continuing our strong efforts after reaching GA and our announcement at the MySQL Users Conference (find a nice press article here).
Alfredo managed to fix a serious bug that almost seemed to be of random nature and happened on certain OnMouseDown and OnMouseUp events on the canvas.
Another thing that got improved is the drawing order of connections between table figures on the canvas. Previously the connections would be drawn on top of tables, resulting in a messy image. Now connections are always drawn behind tables. To make that work we had to remove the nesting of layers - a feature that does not really make sense for a database tool anyway.
The team will meet in the week of May 12th in Kiev where we are going to define the detailed plans for Workbench 5.1 and 5.5. Until …
[Read more]Here are my liveblogging notes from MySQL Sandbox: Easily Using Multiple Database Servers in Isolation by Giuseppe Maxia
Giuseppe has been a community member since 2001, and in the past year or so, a MySQL Employee.
He likes to give things away for free — he gave away T-shirts to the early arrivers to the workshop, and that’s why he’s giving away the sandbox as well. The sandbox is NOT an official MySQL product. It is released from GPL, available from http://sf.net/projects/mysql-sandbox.
Why the sandbox? To be able to set up 1 server in under 10 seconds. And to be able to set up multiple MySQL instances very quickly, and to use them quickly.
The sandbox untars in seconds, for …
[Read more]