We have an Admin plugin for the MySQL Proxy, but people started asking how to use it. I only found one example, thanks to Giuseppe, but people wanted more.

While the admin plugin is somehow limited, it already provides some nice features. One of the use cases is to give access to information to only authorized users. The Admin plugin uses its own username and password to authenticate users. This is not related to any user on your MySQL server.

The example.

I went ahead and put two scripts together in about an hour. They are basic, but should give you more of an idea of what you can do.

Number of queries …

Finding a good db modeling tool for MySQL back in the day was a major pain and always ate up a good chunk of my time. I think I’ve tried just about every db tool on the market. I used to be fond of MicroOLAP’s products. They could handle relatively large models and reminded me a little of the MS Access days. I was then excited about a designer named DBDesigner 4 which was lead by Michael Zinner. It was in its infancy but had enormous potential. Unfortunately, out of nowhere development had stopped on it for what seemed like a year with still many bugs. Shortly thereafter Michael Zinner emerged heading MySQL’s initiative to build a visual design tool named MySQL Workbench seen below.

Now roughly 5 years later, I have to say Workbench is one hell of a design tool. Their stable release supports triggers, …

There seem to be different repeating topics within the Open Source and Geek community.

Koen did a good job explaining how the Great Belgian Firewall reall can't be solved using DNS tricks.

And Giuseppe tackles the ever recurring Sushi. It has to be said ... Geeks love Sushi and not just the MySQl geeks , every conference we go to we try to squeeze in at least 1 Sushi visit.. sometimes more ..... Nurenberg, Manchester, Cambridge, Ottawa , ... and there's more to come .. :)

Technorati Tags: dnsproblems mysql …

A couple of weeks ago I wrote a post titled Dear IBM , I was too late .. I was on holliday last week when people started sending me text messages , such as .. "Game Over MySQL , Long live Ingress" or "No Eclipse for IBM", etc ...

I had ideas regarding the future of certain Sun products at IBM, now the game has changed .. it'ss how they will live on at Oracle :)

Similar Questions arise .. like indeed the future of MySQL, the future of Solaris etc ...

So regarding the future of MySQL , I don't worry at all, on the contrary ..
Oracle tried buying mysql before they already have Innodb .. they didn't kill it .. the MySQL offering is complementary to the Oracle offering, now they can tackle both markets.
And as already mentionned when writing my IBM letter ..

As for MySQL, Jeremey has some good insights.. the fact that …

When it comes to expression evaluation, Mondrian keeps things simple. It doesn't tend to cache the results of expressions, but calculates them each time they are evaluated. Eventually the calculation tunnels through all calculated members and ends up at an atomic cell. Atomic cells are retrieved from the database, and stored in the cell value cache, so they are only calculated once.

By the way, an atomic cell is not necessarily at the lowest level of the hierarchy; Mondrian would prefer to load cells at a coarse granularity, and leave the hard work of aggregating values to the database, or even better, an aggregate table. And Mondrian does its best to retrieve atomic cells in batches. It gathers together requests for lots of cells of the same granularity and generates a single SQL statement to retrieve them all at once.

Mondrian's 'keep it simple' scheme comes unstuck when a particular calculation is repeated many times …

The MySQL Workbench team would like to announce the availability of the first Alpha release of MySQL Workbench 5.2.

The major new feature in MySQL Workbench 5.2 is the SQL IDE, which offers the ability to edit and execute queries on MySQL servers. The new SQL query editor, based on the Open Source Scintilla text editor component, offers full syntax highlighting and other advanced editing features. The SQL editor was also extended to perform live syntax checking, detecting and indicating any syntax errors in your SQL code even before executing them. The IDE also provides ability to browse and edit the contents of individual table rows.

Note, however, that as this is a development version, there are known and unknown issues that might prevent the smooth use of the application. Backup your models often and before opening them with this version as the file format has …

So we've been there.

In my opinion the conference was a great success. Our presentation was not, but that's another story. Percona really showed what conferencing is about. Don't know about MySQL. It was behind the closed doors. Valiant guardians strictly watched that you didn't overhear a word of Sacred Knowledge. Hell, even to get to the Expo hall you had to pay $25 (that's right, you had to pay for watching advertisement) and surrender information about your private life, like your phone number and how you learned about the Expo.

read more

One of the things that has always bothered me about replication is that the binary logs are written to disk and then read from disk.

There is are two threads which are for the most part, unaware of each other.

One thread reads the remote binary logs, and the other writes them to disk.

While the Linux page buffer CAN work to buffer these logs, the first write will cause additional disk load.

One strategy, which could seriously boost performance in some situations, would be to pre-read say 10-50MB of data and just keep it in memory.

If a slave is catching up, it could have GIGABYTES of binary log data from the master. It would then write this to disk. These reads would then NOT come from cache.

Simply using a small buffer could solve this problem.

One HACK would be to use a ram drive or tmpfs for logs. I assume that the log thread will block if the disk fills up… if it does so …

Of the many things I noticed last week at the MySQL Conference, one of the most notable was how many companies have not upgraded from MySQL 5.0 to 5.1 yet. Craigslist is in that camp and it seems that we're joined by the likes of Facebook, Google, Yahoo, and about half a dozen other companies that use MySQL heavily.

Come to think of it, SmugMug are the only folks I've talked with who've made the jump (video).

So it's not much of a surprise that Percona is asking if they should backport 5.4 fixes to 5.0.

Given our usage of MySQL to date, the only really compelling reason to upgrade is to get access to the InnoDB plug-in (and XtraDB). I'd like …

I’m in the process of migrating remaining functionality of Tripod.com from using Oracle to using MySQL. There were some assumptions I had made about various data types, particularly dates. One thing I discovered while converting one piece of code is the Oracle function to_char(). I have a table:

SQL> select member_name, change_time from access_changes where member_name = 'phptester10' order by change_time desc;

MEMBER_NAME          CHANGE_TI
-------------------- ---------
phptester10          13-APR-09
phptester10          13-APR-09

So, I thought “ok, this is just going to be a ‘date’ type with a different format. For instance, 13-APR-09 will become 2009-04-13. But then I stumbled upon a query in a piece of code that does a sort on dates from this access_changes table:

SQL> select member_name, to_char(change_time, 'YYYY-MM-DD HH24:mi:SS') from access_changes where member_name = …