Several months ago I was invited to a special FOO camp at the O'Reilly Campus, about social networking and the social graph. One of the things that the ora people did was record an interview video of each attendee. They've now put all those videos up on youtube.

Here is mine.

Have you ever executed a query from the MySQL command line client only to find that the output wrapped and the result is unreadable? In the past you have to run the query again with \G instead of ; or \g to get it to display the output in a vertical mode. My feature in MySQL 6.0.4 fixes that. The auto-vertical-output option tells the command line client to display the results in vertical format if the results are going to be too wide to display horizontally. It does this without re-executing the query because MySQL passes the length of each column in the result set. If the client isn’t able to determine the width of the screen it will default to 80 chars.

DTrace Integration with MySQL 5

On April 15-16, we demoed a few DTrace probes for MySQL 5.0 integrated with Chime visualization Tool at MySQL users conference 2008. Here is an snapshot of the DTrace probes in chime showing the query execution time/count in Chime tool:

The DTrace probes inserted into MySQL 5.0 in the demo are:

provider mysql {
    probe data__receive__start(int);
    probe data__receive__finish(int);
    probe query__plan__start(char *);
    probe query__plan__finish(char *);
    probe query__execute__start(void *, char *, char *, …

Just updated the datagrid so if you don't specify an ORDER BY clause, ordering will be disabled. You can if you wish either not specify an ORDER BY clause (in which case ordering will be disabled), or you could specify one to get your rows ordered how you want, and then set the allowSorting property to false to disable ordering.

Bear in mind that this is the development version, but it will probably be released soon.

Just updated the datagrid so if you don't specify an ORDER BY clause, ordering will be disabled. You can if you wish either not specify an ORDER BY clause (in which case ordering will be disabled), or you could specify one to get your rows ordered how you want, and then set the allowSorting property to false to disable ordering.

Bear in mind that this is the development version, but it will probably be released soon.

Since I've been pinged about this a couple of times the answer is that I know of no plan to close source the Archive Engine's backup program, archive_reader. No one has removed it from the 5.1 tree, in fact no one has approached me about it.

Hell, I doubt most even know that it is there :)

I was just reading Fabrizio Capobanco’s take on the MySQL excitement (”this move is clearly into the right direction”) when it occurred to me that the situation is related to the comments recently made by the former CTO of Kaplan Test, Jon Williams, at the recent OSBC conference.

As I wrote at the time: “Another point Jon made was that the subscription model helps keep open source vendors on their toes as every year he gets to decide whether they will received another payment.”

In other words, as …

Two great posts were written over the weekend on MySQL, and I'd encourage you to read both. The first is from Pierre @ Milking the GNU who has some ideas for how MySQL/Sun can make money with a 21st-century software business. The second is from Glyn Moody, wondering if ...

DTrace Integration with MySQL 5

On April 15-16, we demoed a few DTrace probes for MySQL 5.0 integrated with Chime visualization Tool at MySQL users conference 2008. Here is an snapshot of the DTrace probes in chime showing the query execution time/count in Chime tool:

The DTrace probes inserted into MySQL 5.0 in the demo are:

provider mysql {
    probe data__receive__start(int);
    probe data__receive__finish(int);
    probe query__plan__start(char \*);
    probe query__plan__finish(char \*);
    probe query__execute__start(void \*, char \*, char \*, …

DTrace Integration with MySQL 5

On April 15-16, we demoed a few DTrace probes for MySQL 5.0 integrated with Chime visualization Tool at MySQL users conference 2008. Here is an snapshot of the DTrace probes in chime showing the query execution time/count in Chime tool:

The DTrace probes inserted into MySQL 5.0 in the demo are:

provider mysql {
    probe data__receive__start(int);
    probe data__receive__finish(int);
    probe query__plan__start(char \*);
    probe query__plan__finish(char \*);
    probe query__execute__start(void \*, char \*, char \*, …