The phpMyAdmin project will be participating in the DotOrg Pavilion at the MySQL Users Conference. Marc even put up a banner for it on their site - thanks!

There's a whole range of UC banners available at http://mysqluc.com/images/mysqluc2006/banners/ (they should link to http://www.mysqluc.com/)

Whenever we are faced with a choice between two designs, and the first design is upward compatible with the second (i.e. the first design is more restrictive, and implementing design two would not affect functionality provided by design one), and the full impliciations of the second design are not yet known, the first design choice is recommended.
Formulated by C.J. Date in "Relational Database: Writings 1989-1991"

MySQL 5.0 has a ton of new features. In fact, several tons. Many people and companies were waiting endlessly for some of these features. Some of the new features include: Views, Stored Procedures and Stored Functions, Triggers, and some extra optimizations. Hoorah.

However, not all is peaches. In fact, there are few peaches to be found. Consider the rest of this post a bitch/complaint session and a call for a return to sanity. Let’s take a look at some of the major features of MySQL 5.0:

Views — Views are a …

In anticipation of getting my sunfire , and doing some real benchamrks with it, I thought I’d do a quick, test to see if I can still do them..kind of like a warm up excerise before you do a 1500m swim.

So I grabbed 2 idle machines I have access too, and see how mysql 5.1 performed on both.

I took Brian’s mysqlslap tool and gave it a little whirl.

the 3 boxes I had in my aresenal are

• dual x86-64 @2.4G with 8G of ram

a

• 280R with 2 Ultrasparc III+ processors and 4G of ram.

and my new macbook

• a Intel Dual processor shiny thing

now in their time, both of these boxes were considered pretty sweet. (the 280R was purchased in 2002 I think, and for financial people just nearing the end of it’s lifecycle so you will still …

Dear MySQL users, MaxDB users and friends,

Several co-workers have spoken to me on the length of the MaxDB series postings. I fully agree that most postings are too long for a blog. But we do have a very eager plan to publish a complete online class. This is causing long postings and we can’t make them much shorter. We try to structure the articles in a similar way like a web page to make reading and navigating easier. Every posting has a table of contents, is devided into sections and has a fixed structure. For offline reading, printing and as a reference we will soon publish a PDF document with all postings of the series.

The experiment to use the medium of a blog for a class will continue as long as the readers do not complain. But we will add a “read more” link to the fixed structure of every posting. That means, we will present only the beginning of a posting on PlanetMySQL and you have to click on a “read …

Dear MySQL users, MaxDB users and friends,

Several co-workers have spoken to me on the length of the MaxDB series postings. I fully agree that most postings are too long for a blog. But we do have a very eager plan to publish a complete online class. This is causing long postings and we can’t make them much shorter. We try to structure the articles in a similar way like a web page to make reading and navigating easier. Every posting has a table of contents, is devided into sections and has a fixed structure. For offline reading, printing and as a reference we will soon publish a PDF document with all postings of the series.

The experiment to use the medium of a blog for a class will continue as long as the readers do not complain. But we will add a “read more” link to the fixed structure of every posting. That means, we will present only the beginning of a posting on PlanetMySQL and you have to click on a “read …

Last night I returned home from our internal MySQL Developer Meeting in Sorrento, Italy. The trip again was uneventful (something I certainly don't mind) and I used it to catch up with email and other work that I could not take care of while being at the conference.

The event was very well organized (kudos to Carol and the rest of the team!) and I enjoyed meeting old and new colleagues. It was nice being able to discuss stuff from face to face and hearing about what's cooking at the various other parts of the company in more detail. Too bad that we sometimes had so many tracks in parallel - it was difficult at times to decide which session to attend without fearing to miss something else. I gave a presentation about SUSE Linux (why it's the best Linux distro to use) and how our developers can help to foster our user community.

On Monday evening, we arranged a small meeting with local community users, some of them …

I am excited to announce that the phpMyAdmin project confirmed to be present at the DotOrg Pavilion of our MySQL Users Conference in Santa Clara next month. Thanks a lot to Marc Delisle for the quick reply and arrangement of a representative. One more good addition to the excellent program we've already lined up!

By the way, we still have some open slots to give away for interested projects! So if you're a developer or member of an Open Source project that utilizes MySQL, here's your chance to show off your work to a very special audience. The exhibition will be open on Tuesday and Wednesday, but we'll provide each project with one free conference pass that will entitle you to …

http://www.regdeveloper.co.uk/2006/03/07/borland_ditches_delphi/

Yet again I have been on the MySQL forums and yet again it's given me something to write about. The question was pretty standard simply asking how you comment out code or add comments to MySQL stored routines. However the wording of the question got me thinking. In the past when I have been writing complex stored procedures in Oracle it can be difficult to see where an error is coming from, not necessarily which line is raising the error but which section of code cause the problem. One of the methods I have used in the past is to use the /* */ multi line comment syntax to exclude blocks of code on mass to rule them out quickly, this has proved a good way to narrow down where the root of an error comes from.

But as you may know MySQL simply removes any comments from the code if it's entered via the command line, it makes no distinction between comments you are adding and code which has been commented out. This isn't a problem when you …