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 …

The GUI tools team at MySQL has been working hard on a number of new releases including an update to the Migration Toolkit that provides many bug fixes as well as support for a broader range of source databases.  You can use the Migration Toolkit to go from any JDBC-supported database to MySQL 5.0 and there are also optimized migration modules for several versions back as well as the most recent versions of Oracle10g, Oracle XE, SQL Server 2005 and Access.

You can get the latest Migration Toolkit 1.0.25 below:

• MySQL: Migration Toolkit Downloads (1.0.25)
• MySQL: Migration …

Twice a year, the training team meets to discuss things, and also to have a good time. This is my second meeting since I joined the team 9 months ago. Last time, it was London, now we?re in Las Vegas, Nevada, USA.

Yes, we?re here for work. We arrange new training material, upcoming schedules, improve internal processes, create partner programs and much much more. Besides that such meetings are important to meet face to face with your coworkers, usually we just communicate remotely. Also, we have some new collegues around that are introduced into the team.

And following the ?Work hard, play hard? rule, we also enjoy Las Vegas. Never been here, it?s an insane place. Some great hotels with of course lots of casinos. Too bad our boss is not approving all the expenses. But I can recommend to visit this …

It's pretty rare that I come across a bug in MySQL, but the few times I have I'm impressed at the kind of response that comes from the developers. Yesterday's bugs (filed late last night) were verified by mid-morning. I had marked both of them as severity S3 (non-cricical) but turns out one is reclassified as S1 (critical) because it's causing a server crash (as opposed to a client disconnect as I thought). It seemed trivial, a connection loss caused by a syntax error on setting up disk-based storage. Then again, nobody wants to fear that if they type their SQL incorrectly it might bring the server down.

I guess verification and resolution are two different things, but it's nice to hear back quickly. I'm glad these aren't happening in a production environment because I'd be hoping for verification and a fix by now.