Ok, so it's only in the architecture stage... but the great news is, we're already publishing the info so we can get early feedback before implementation starts. I think that's a fab development. Greg Lehey is leading this project.

You can find the review document here: OnlineBackup (on the MySQL Forge Wiki).

This feature will implement a way to make complete online backups (i.e., from a running server), regardless of which storage engines are being used. A backup will also be consistent across multiple engines.
And the idea is to make it a stream, so it can be sent straight through gzip/bzip, or tape or some other sequential archival device. This is excellent for very large data sets, of course, as there wouldn't be space for …

As part of both my UltimateLAMP side project, and my greater involvement with MySQL Workbench, I’ve been wanting to review and document the database schemas of Open Source products.

Indeed, as part of discussions with Mike Zinner of MySQL AB at the recent MySQL Users Conference, I suggested an idea used in the Java World, for example by Clover and Agitar, where to promote the usefullness of their respective tools (in this case code coverage), they provide results against Open Source Products. For an example check out Clover Examples.

With MySQL Workbench, to get some greater …

This interview took place with Monty Widenius, co-founder of MySQL, at his house outside of Helsinki, Finland. In Montyâ??s usual understated Finnish style, we talked about MySQL 5.0, coding styles and cooking.

In this issue of the MaxDB series we will introduce you to some selected aspects of transactions. The topic of transactions seems pretty boring. But in fact it depends very much on the point of view you take. We have tried to put a light on the subject that shows some rather advanced aspects of transactions which are a little less often discussed in database classes.

Tokyo ? Smart Style Co. Ltd., the MySQL solution experts in Japan, today announced that it has extended its membership in the MySQL partner program in order to expand its MySQL sales activities throughout Japan.

In MySQL, privileges are stored in tables in the mysql database, so if I have UPDATE privileges to that database, it’s easy to update my own privileges. For an example of what the desired privileges should be, run the following query: select * from user where User='root'; The Grant_priv column is what I’m interested in. I just update that value to ‘Y’ for my user, execute FLUSH PRIVILEGES, log out, and log back in.

Last month I blogged about the silly changes to the default for the SHOW STATUS command in MySQL 5.0 in Stop the madness: SHOW STATUS, and I filed MySQL Bug #19093: SHOW STATUS defaults to SESSION.

Well, it looks like Monty has spoken and this will not be fixed. That’s unfortunate, but oh well, I tried.

You can read the full text of Monty’s reply in the bug report itself, but his reasons for supporting the current behaviour boil down to:

• It’s similar to what SHOW VARIABLES does. — Yes, this is true, but neither commands’ output makes sense, really. If you do SHOW [SESSION] STATUS, you get a mix of session-scoped and global-scoped results back, and there’s no way to tell which is which. Same goes for SHOW [SESSION] VARIABLES. Ugh.
…

Test

I ran across this article while going through some of the articles on Planet MySQL. The article is about how to properly file a bug report. It’s very well written, you can find the article here. If you use software, you need to read this. (That means all of you do).

The post that took me to this article, is here.

Tags: bug reports,, software qa