Starting from tomorrow (1st of June) I will officially become an Oracle employee. It is quite funny how many companies you can change without even applying for another job. ;-)
I've been hired by MySQL in the beginning of 2008, a few months later it has been acquired by Sun and after about a year we've been acquired again, this time by Oracle.

I personally consider this a new beginning and I join Oracle with a lot of enthusiasm. After all I'm now part of a company that has a huge set of products and technologies and it is like a playground for me.

I'm afraid I've not blogged frequently in these months, but I plan to write more and more in the future. This short post is just to wish good luck to all the Dolphins who have joined Oracle and all those who are swimming in a different ocean.
…

This blag was originally posted at http://cafuego.net/2010/05/26/fast-paging-real-world

Some time ago I attended the “Optimisation by Design” course from Open Query¹. In it, Arjen teaches how writing better queries and schemas can make your database access much faster (and more reliable). One such way of optimising things is by adding appropriate query hints or flags. These hints are magic strings that control how a server executes a query or how it returns results.

An example of such a hint is SQL_CALC_FOUND_ROWS. You use it in a select query with a LIMIT clause. It instructs the server to select a limited numbers of rows, but also to calculate the total number of rows that would have been returned without the limit clause in place. That total number of rows is stored in a session variable, which can be retrieved …

The primary responsibility of MySQL professionals is to establish and run proper backup and recovery plans. The most used method to backup a MySQL database is the mysqldump utility. This mysqldump utility creates a backup file for one or more MySQL databases that consists of DDL/DML statements needed to recreate the databases with their data. To [...]

Let's start with the plugin. The documentation has been updated to cover this new feature. And 27 new tests give me some confidence that it …

Having a reverse-proxy web cache as one of the major infrastructure elements brings many benefits for large web applications: it reduces your application servers load, reduces average response times on your site, etc. But there is one problem every developer experiences when works with such a cache – cached content invalidation.

It is a complex problem that usually consists of two smaller ones: individual cache elements invalidation (you need to keep an eye on your data changes and invalidate cached pages when related data changes) and full cache purges (sometimes your site layout or page templates change and you need to purge all the cached pages to make sure users will get new visual elements of layout changes). In this post I’d like to look at a few techniques we use at …

After having updated to the latest build via Help > "Check for updates" you will be able to see more than only the result of the last SELECT query in any "Query" tab. By default, HeidiSQL displays up to 10 result sets in subtabs. In case you want more just go to

Tools > Preferences > Data

and increase this value in Maximum number of query results. Different than before, these are the first result sets from your SQL code.



Please note that HeidiSQL still does not separate multiple results from a stored procedure. Will be the next thing to implement soon.

Also a minor new feature is the hint on the lower statusbar when hovering over the MySQL version. You will see various connection, server and client related details here.

Anirudh Tamsekar made a post yesterday that laid out a few of the limitations of MySQL Cluster that seem to cause him the most pain. However his assessment of the situation is quite misleading. A few of his statements are inaccurate but more than half of the limitations he cites to are out right false. Since comments on Anirudh's blog are being moderated, I give my rebuttal here, and cite sources.

· Database names, table names, and attribute names cannot be as long in NDB tables as with other table handlers. In NDB, attribute names are truncated to 31 characters, and if they are not unique after truncation, errors occur. Database names and table names can total a maximum of 122 characters

False: "Identifiers. Formerly (in MySQL 5.0 and earlier), database names, table names and attribute names could not be as long for NDB tables as tables using other storage engines, because attribute names were truncated …

While I use this tcpdump command for MySQL query analysis with mk-query-digest, I found recently that it didn’t work on FreeBSD

$ tcpdump -i bge0 port 3306 -s 65535 -x -n -q -tttt -c 5
tcpdump: syntax error

It left me perplexed and reading the man page seemed to indicate my options were valid. I tried a few variances just to be sure without success.

$ tcpdump -i bge0 -c 5 port 3306 -x
tcpdump: syntax error
$ tcpdump -i bge0 -c 5 port 3306 -q
tcpdump: syntax error
$ tcpdump -i bge0 -c 5 port 3306 -tttt
tcpdump: syntax error

The solution was actually quite simple in the end, it had nothing to do with the commands, it had everything to do with the order of them. Placing port as the last option solved the problem.

$ tcpdump -i bge0 -s 65535 -x -n -q -tttt -c 5  port 3306

$ uname -a
FreeBSD …

Here are some tips that have been recently published on Java EE 6 & GlassFish: