I have not finished MyQuery 3.4.0, after a long time of weekend and spare-time development. This version adds some features that are basically Scintilla featires that I have integrated with. This includes error indicators, margin markers and some other things. In particular the margin markers changes a few things in the interface: When running up to, or continue from a point in teh script, then use the margin marker instead of the current line! If you don't like this, then don't set the margin marker and the current line will be used just like in old releases.

Another addition this release is Online help. I get the help contents from the database that you connect to, which is installed with most MySQL installations in the tables called help_xxx in the mysql schema.

External program has a few more options, and in this release the installer installs a …

I wish I could go to PGWest this year. A lot of great work has been done on PostgreSQL in the last year and a half. There’s a new release with built-in replication, and there are in-place upgrades. That solves two of what I think are its three biggest shortcomings in many large-scale database deployments. (Lack of index-only queries is the third shortcoming.)

PGWest is the first major conference about Postgres since the 9.0 release, so all the cool stuff is happening there. I encourage MySQL users to go to it as well — there is a lot to learn from PostgreSQL. Just remember to be polite and don’t start, encourage, or tolerate any sniping between MySQL and Postgres fans.

Related posts:

1. Postgres folks, consider …

As I have previously stated it is quite rare that I blog about my feelings about things going on with Oracle in the MySQL community, others do this a lot better than me, but a blog post I’ve seen today has pushed me to write something about how I feel.

To me it implies that IOUG are trying to put themselves as the leaders of the MySQL community.  I personally feel that they need to earn our trust first before trying this move.

I see that they mention the Collaborate conference, but no mention of the O’Reilly MySQL Conference & Expo …

Independent Oracle User Group's (IOUG) President, Andy Flower's article in the latest issue of Oracle Magazine extends a warm welcome to the MySQL community!

Andy outlines a number of ways in which they are collaborating with the MySQL users and community. Here is an excerpt...

IOUG is looking forward to providing a platform for MySQL users to gather virtually and physically year-round. To start, we are helping support local MySQL events, such as OpenSQL Camp in October 2010 in Boston, Massachusetts.

But we are most excited to present 120 MySQL educational sessions, given by MySQL users and key industry partners, which will be held at our annual COLLABORATE conference in Orlando, Florida, April 10-14, 2011. Not only will there be a special focus on MySQL, but attendees …

Mea Culpa, Mea Culpa, Mea Maxima Culpa!
My fault, my fault, it’s all my fault! Why? Well because new versions = new bugs :) = wait till they are fixed, then use it!

As an ubuntu fan I just had to install 10.10 GA … and as a MySQL DBA I can’t run apt-get install mysql …. not even in my nightmares can I do that. Why? Well because if you are a car mechanic you don’t take your car for repairs to another mechanic and not ask what was done on it do you? You do it yourself right? That is what I did, I installed mysql 5.1.50, the same binaries I had downloaded and used on my 10.04 machine and loaded a dump. Woops, mysql crashed big time. I figured, lets install 5.1.51, load and … boom, again crashed.

The same dump, is loading fine on my 10.04 ubuntu server running both 5.1.50 and 5.1.51.


101018 12:48:26 - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that …

When you are working with MyISAM [1] tables MySQL provides a feature called the Midpoint Insertion Strategy [2]. You can enable it with the parameter key_cache_division_limit [3].

By default, the key cache management system uses a simple LRU [4] strategy for choosing key cache blocks to be purged:

When using the Midpoint Insertion Strategy feature, the LRU chain is divided into two parts:

• the hot sub list

and

• the warm sub list.

The division point between those two parts is not fixed, but the key …

Bradley M Kuhn published an interest blog post at the weekend explaining why he believes Canonical is about to go down the open core licensing route and heavily criticising the company for doing so.

My take on the post is that it is the worst kind of Daily Mail-esque fear mongering and innuendo. Not only does Bradley lack any evidence for his claim, the evidence he presents completely undermines his argument and distracts attention from what could be a very important point about copyright assignment.

The premise? Mark Shuttleworth has admitted that he plans to follow the open core licensing strategy with Canonical.

The evidence? Mark praises the strategy Trolltech took of selling proprietary licenses.

The problem? Trolltech did not follow the open core licensing strategy. Neither did MySQL, which Bradley suggests …

Next time you have an error whilst running an sql script into mysql using the pretty easy redirect into eg: mysql -uroot -pmsandbox -h127.0.0.1 -P3306 dbname < filename you might want to give the -v option a shot.

MySQL normally outputs an error with the line number like:

[mysql@dcassar-ubuntu /mysql/dumps/stored_procs 11:10:12]$ mysql -uroot -pmsandbox -h127.0.0.1 -P5151 test < file
ERROR 1267 (HY000) at line 375: Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (latin1_general_cs,IMPLICIT) for operation '='


But 375 is not including comments and stuff so it’s a bit hard to go through the file to locate the exact section which is failing.

Run the same command with -v:

[mysql@dcassar-ubuntu /mysql/dumps/stored_procs 11:10:30]$ mysql -uroot -pmsandbox -h127.0.0.1 -P5151 -v test < file | tail -5
ERROR 1267 (HY000) at line 375: Illegal mix …

It seems obvious that given the decreasing cost of storage and computation, there's going to be a significant increase in the volume of data that organizations accumulate over the next 10 years.  But the type of data being accumulated may be different from the areas where traditional DBMSs dominated.  It's not just about transactions; it's search patterns, on-line behavior, click-thru data, events fired off by smartphones, messages over Twitter & Facebook, log data of various kinds.

If an organization can figure out a better way identify prospects, or deliver more targeted ads, or optimize pricing decisions by analyzing terrabytes of data, they'd be crazy not to. Over the long term, companies that don't develop these capabilities will be at a competitive disadvantage.

As to what the implications are from a …

As of today I have a new employer, and I no longer work for MySQL / Sun / Oracle, instead I am now Database Architect at Recorded Future (http://www.recordedfuture.com). This is exciting stuff, really so. RF pulls data from teh Web, but instead of just allowing searching, RF will analyze what it find to spot trends and things like that.

It is still early days, we need to collect a lot more data than today, and managing that will be one of my challenges. But an interesting and fun challenge!

This doesn't mean I will not maintain MyQuery anymore, I sure will. And Recorded Future is by the way MySQL users, so I will probably work even more with MySQL related stuff than today. I will also continue to blog about what we are doing, and about other database related things as well. In particular, …