MySQL Users Conference 2006 - April 24-27, 2006 - Santa Clara, CA

I’m presenting “MySQL Cluster: New Features and Enhancements”. It’s going to be a riot. Lots of sexy new stuff to go on about. I’ll also be running a Cluster BoF and am really looking forward to chatting to people about Cluster and what we can do to make it better for our users.

So come along and talk to me while I’m there.

I’ll be sure to use the word “thongs” in the Australian sense as much as possible.

So come along, or I’ll be forced to ask “Where the bloody hell are ya?“

MemberDB - A Membership Database

I released 0.4 today. A rather long awaited release. No doubt there’ll be bugs and the need for a 0.4.1 or something - but this is relatively bug free and has a bunch of new cool stuff to chew on.

It’s also the first real release to support MySQL 5.0 (previous releases won’t work as MemberDB heavily uses views).

So, I didn't get to meet Oracle's Monica, mainly because she kinda vanished. I had my own talk after hers, and when I went downstairs to the exhibition she was already gone. The Oracle booth had a few people manning it, but not much crowd.

Same for the Sybase stand, actually. They had a video running, explaining how they'd been the first database doing this and that.... not sure how much that actually impresses people, pointing to the glorious past.

MySQL didn't have its own booth this time, but I toured round Tuesday and Wednesday, met many interesting people and was introduced to even more. I found that MySQL truly has a lot of friends, both big and small. And apart from our big partners (HP, Novell, Red Hat, IBM), many if not most of the smaller booths were actually companies who deploy their solutions on MySQL. That was a nice surprise! …

MySQL has started a MaxDB series on its corporate blog aggregator. Since the beginning of Februar the MaxDB team tries to write one MaxDB article per week for you. The articles get published on our english language web site http://www.planetmysql.org. All articles together will make a complete MaxDB class. The class describes the use of MaxDB as a stand-alone enterprise database. We do not discuss the use of MaxDB with SAP applications.

As it turns out, the memory leaks which I initially blamed on 5.0 also affect 4.1. It’s not stored procedures leaking memory as I initially thought, but server-side prepared statements. The problem was finally worked out by setting useServerPrepStmts=false in the JDBC code, which “fakes” prepared statements on the client side, without any other code changes.

Read MySQL Bug #18300 for more information!

At the recent MySQL DevConf in Sorrento, Italy, I decided to take a photo out the window of my hotel room. Here it is. I’ve stayed at worse places, just :)

It also looked really similar to this from the breakfast and lunch room.

Pity we were then stuck in the basement working for most of the day. But it rocked. Got through lots of stuff, which is good.

the mysql users conference 2006 is only a month away. i?m just going to be dropping in for one day to give two talks ? ?embedding mysql? and ?practical i18n with php and mysql.?

there is also a great lineup of other speakers, tutorials, and keynotes. i?m going to miss the keynote by mark shuttleworth, but i am looking forward to the keynote by the founder of rightnow.

First afternoon session for PHP Quebec is An Introduction to PostgreSQL by Robert Bernier.

"PostgreSQL isn't hard, it's just loaded with details." Robert says the goal of the presentation is to make the audience curious enough to go play around with PostgreSQL. PostgreSQL documentation is superb.

History

Relational databases started with Ted Codd breaking data into concepts using language for breakpoints. IBM, Oracle (or what was to become Oracle) and Cal Berkeley took the idea and started development. Postgres was an idea developed at Berkeley by lots of students. This was in the late 60s & 70s. Informix is based on Postgresql, bought by IBM now. Oracle and SQL Server has PostgreSQL code in it too. Pretty much every database except MySQL has some PostgreSQL in it.

Open …

The newest MySQL baby!

Born 2006-03-30 00:30:00

8lb 4oz

21.5 inches

Mom and baby are doing great.

(Click to enlarge)

Earlier this week, I wrote about the Synchronization Manager and gave a step-by-step tutorial on getting an initial scenario implemented. In this article, I’ll expand on the previous tutorial by introducing the concept of uni-directional synchronization.

Uni-directional participants act as destinations for replicated data. These participants are sometimes called “slaves,” because they are not capable of replicating changes to other members of the synchronization scenario. Theoretically, any RDBMS that provides an appropriate JDBC interface can participate as a replication destination with little effort on the part of the DBA. As an example of this, I have documented my experience creating a uni-directional MySQL participant.

One situation DBAs might use databases synchronized as uni-directional participants is when they want to provide information to clients …