You maybe already noticed, that MariaDB folks released their new stable version 5.2.3 today. And as we've got our great openSUSE Build Service, we already have this version packaged and you can install it easilly on openSUSE. I didn't had much time to test it deeply, I just tried that it runs, and that I'm able to connect to it, so it is currently in serveratabase:UNSTABLE repository, but after some testing, it will proceed futher If you want to try it, make sure to backup your data first! So on openSUSE you can use one click install to get MariaDB 5.2.3. For others, you can just use one …

You maybe already noticed, that MariaDB folks released their new stable version 5.2.3 today. And as we’ve got our great openSUSE Build Service, we already have this version packaged and you can install it easilly on openSUSE. I didn’t had much time to test it deeply, I just tried that it runs, and that I’m able to connect to it, so it is currently in server:database:UNSTABLE repository, but after some testing, it will proceed futher If you want to try it, make sure to backup your data first! So talks on openSUSE you can use one click install to get MariaDB 5.2.3. For others, you …

Now it's two and a half year since the last refactoring of HeidiSQL's dialog for editing user accounts. The current dialog was ok from a usability point of view, but it did not allow users to assign routine privileges on newer servers. And it edited and created users by updating the tables in the mysql db directly, which is error prone, complex and not recommended by MySQL.

The new dialog now does all updates by GRANT, REVOKE, RENAME USER and SET PASSWORD, as recommended by MySQL. The GUI has also evolved:
- you can clone users now
- the entered password must be repeated
- privilege names are painted in different colors for read, write and admin relevance
But see yourself:



To get it, just go to Help > Check for updates and install the latest build.

Now it's two and a half year since the last refactoring of HeidiSQL's dialog for editing user accounts. The current dialog was ok from a usability point of view, but it did not allow users to assign routine privileges on newer servers. And it edited and created users by updating the tables in the mysql db directly, which is error prone, complex and not recommended by MySQL.

The new dialog now does all updates by GRANT, REVOKE, RENAME USER and SET PASSWORD, as recommended by MySQL. The GUI has also evolved:
- you can clone users now
- the entered password must be repeated
- privilege names are painted in different colors for read, write and admin relevance
But see yourself:



To get it, just go to Help > Check for updates and install the latest build.

A lot of the work that I do on my personal projects such as Flexviews and Shard-Query involves taking a query and manipulating it in such a way as to obtain the same result, but in a different manner.  Flexviews amortizes aggregation over time, making it possible to maintain summary tables incrementally. Shard-Query (http://code.google.com/p/shard-query) spreads queries over multiple Gearman workers, allowing it to run queries on one or more MySQL servers in parallel.

Both of these tools rely on a similar set of substitution rules.  One of my favorite parts of various math classes was learning how the different mathematical expressions could be substituted for one another, allowing you to solve what otherwise appeared to be impossible problems.  Using simple substitutions, SQL can be made to solve difficult problems too, such as running queries in parallel or on multiple shards (or both).

I've tried to …

I just saw that MySQL 5.5.7 RC had been released, and reading the releasenotes made me more than a fair bit suspicious. In some kind of general agreement on what constitutes a "beta" release, this is when the software has reached a level of maturity when no more major features are to be introduced. MySQL (and many others) has broken that rule at times, and the rule is not enforced or something.

What constitutes an RC release though, in my mind, but I really want to know what you think, is software that is really 100% feature complete. There may be, but hopefully there aren't, even any major bugs to iron out. In short, it is "A Candidate to Release", and as close to GA as you can get. I have not seen this rule broken much, really.

With MySQL 5.5.7, this is an rc, as was the previous release, 5.5.6, and this time there is a really major feature introduced between these two release, pluggable authentication. And before I …

I’ve started an HTML manual for innotop, a “top” clone for MySQL. It includes screenshots. Right now I only have screenshots for the new U mode, which demonstrates how the User Statistics enhancements in Percona Server can show you which tables and indexes are most used.

No related posts.

The confusion about whether MySQL Community Edition still included InnoDB seems now to have dissipated. Thank you to Sheeri Cabral, Darren Cassar and all of you who helped correct the misperception created by catchy headlines. In part, the confusion was caused by people assuming that the MySQL Classic Edition (an option for embedding that has been around for a long time) is the same as MySQL Community Edition...not so. We have made appropriate changes to our web page to …

A very interesting presentation by Kaj Arnö about the State of the MySQL Community. The initial part of the presentation is about the history of how things happened with MySQL, Sun and Oracle, then it describes the current state of our community. The final part of the presentation is fairly enough promotion towards SkySQL for whom Kaj is EVP of Products. I really enjoyed it and would recommend it to all of you interested in past, present and future of “MySQL”.

check it out here

Disaster struck again. Well, it’s actually not really a disaster. db4free.net is a testing environment and people are not supposed to use it for any important data, or to use it in production. When after the last server update the main server instance started crashing, it was one of these circumstances which I can’t guarantee my users not to happen, and since both my budget and the server resources are low, I can’t afford setting up a backup system which allows me to restore everything just as a commercial database provider can (or should be able to) do.

Unfortunately I received a few emails (sorry that I couldn’t answer all of them directly) which made me believe that this fact isn’t obvious to all users. Even though the Conditions of Use pretty much explain that, not everybody obviously reads them. Which is why I added this text to both the registration form and to the registration email, so that it leaves no doubt that every …