GUI Interfaces to use with MySQLWhen meeting with MySQL customers I always get asked about GUI interfaces.I am always asked, what GUI to you recommend with MySQL? Two of the most popular are SQLYog and Navicat for MySQL customers.Looking at Oracle SQL DeveloperI think it is time to see how well SQL Developer works with MySQL. Oracle's SQL Developer has matured into a very nice tool and its

I’ve just come across the following post on new 5.1 and 6.0 replication features which was quite interesting.

A few features mentioned such as:

• pluggable replication architecture
• semi-synchronous replication
• time-delayed replication
• scriptable replication

sound like things what are going the right way. For those of still using 5.0 we’ll have to wait for quite a long time before we will actually be able to use them. At least some of this gives us an incentive to upgrade.

No mention yet of N:1 replication, or making the replication process separate from the main mysqld process. The latter is much easier now and would only require minimal hooks in a plugin at each send of the replication path. However, these are things that can come in the …

This is rather a theoretical interest for me for now (what else to do Friday evening) , but I see how it can be used in current dual-licensed mixed open / closed source storage engines MySQL world.

So problem is:

Let's keep MySQL aside for simplicity and imagine we have fully open-source GPLvX licensed "MoonOffice" software. MoonOffice uses libsupercompress library which also distributed under GPL, and provide two functions: "superCompressFile", "superDecompressFile". MoonOffice can be both statically or shared linked with this library. This all fine.

Now imagine one provides library libquickcompress, which is closed sourced, available only in binary formats .so and .la, but the license on it is "use it as you want, link it with whathever you want, distribute it as you want". Of course library also exports two functions "superCompressFile", "superDecompressFile".

Now questions: can we link our GPLed "MoonOffice" …

In April we introduced Instant Findability, TED video embeds, a springtime theme, a cool new domain, and reply-by-email for comments, now open to all. A pretty busy month, with more awesome features on the way, plus WordCamp San Francisco, on May 30.

If you’re in town or want a reason to be, be sure to register soon. We’ve …

So how is the regression issue coming along?

Glad you asked!

Earlier in the week Jay found that the bitset patch gave us significant regression. This particular patch was a move from using a built in bitmap system MySQL had, to using the bitset found in the standard template library.

Since then we have been able to find issues with it, but no conclusion on how to solve it via a new design/container/etc.

So what are we doing?

Earlier this week I refactored the interface to the Table objects to create, well, an interface!

It is not perfect but it encapsulated a large chunk of the code. Monty today put back into the original MY_BITMAP but did so behind this interface. Jay has run the numbers and declared that the regression can no longer be found.

What will happen from here?

We are going to work on the interface some more. …

A while ago I posted about a comment a Sun performance engineer made about a scalable replacement for InnoDB. At the time, I did not believe it referred to Falcon. In hindsight, it seems even clearer that the Sun performance experts were already working hard on InnoDB itself. Sun’s engineers have shown that they can produce great results when they really take the problems seriously. And I’m sure that InnoDB’s performance has untapped potential we don’t see right now.

Came across an error on the sql for the overview.php page. It wasn’t correctly displaying aggregate data on the charts. So here’s the fix for rev50 to rev51. This isn’t a deal breaker on the release but if you’re inclined to open system/application/models/model_main.php and replace one line it’s easier than waiting for our next release.

2001c2001
< $sql = "select $xval,DATE_FORMAT(Creation_time,'%m-%d %H:%i') as Date from server_statistics WHERE Creation_time BETWEEN '$sday' AND '$eday' GROUP BY DAY(Creation_time),HOUR(Creation_time) ORDER BY Creation_time";
---
> $sql = "select max($xval) as $xval,DATE_FORMAT(Creation_time,'%m-%d %H:%i') as Date from server_statistics WHERE Creation_time BETWEEN '$sday' AND '$eday' GROUP BY DAY(Creation_time),HOUR(Creation_time) ORDER BY Creation_time";

Nice changes in this release. We have a new tab on the host page for “Variables” which contains three sub tabs: “cnf file”, “global variables”, and “global status”. These tabs display the most recent information gathered from your servers in the event that you would like to see the raw data that is going on. It’s also nice to be able to refer to this data without having to login to the server to get it.

As usual, you can download the new release here: http://kontrollsoft.com/software-downloads

When we sat down at an Austin cafe in 2005 and wrote the stats system, Matt and I had no idea what we were getting into. He created the databases and drew the little smiley face while I wrote the code. We had milk and cookies. It was really cute. We were naïve!

I swear it was Matt’s idea to store stats data as daily summaries in Universal Coordinated Time (UTC), which is why stats days have always ended at odd hours for non-Greenwichians. But even if I seem blameless, I failed to champion your cause soon enough. It is even more my fault than Matt’s.

And so today I present a gift. If you have set your blog’s time zone, your stats reports will honor that setting (in whole hours from -12 to +14). This upgrade is retroactive to the beginning of 2009. It affects all blogs using WordPress.com stats, even self-hosted blogs using the Stats …