After a few posts on Devshed forums I decided to summarize some basic directions about porting SQLServer triggers to MySQL.
There are some notable differencies between trigger syntax in SQLServer and MySQL (and other databases in general).
First of all usually you reference old (preexisting) and new (inserted or updated) column values by NEW.column_name and OLD.column_name, but in SQLServer those values are held in two tables named INSERTED and DELETED, on which you'll have to perform selects.
Second relevant difference is that SQLServer doesn't have BEFORE triggers, you'll have to use a rather convoluted syntax for this.
Third difference is that one SQLServer trigger can fire upon multiple actions (one single trigger for insert/update/delete).
Fourth difference, as new/old values are held in a table there is no FOR EACH ROW implicit loop but you'll have to …

My talk at the MySQL Users Conference went well. MySQL For Oracle Developers was part of two talks, the second was by Mark Leith on MySQL For Oracle DBA’s.

I had a number of positive comments from attendees, including Ken Jacobs of Oracle who also contributed some valuable information in comparision of UPDATE/DELETE ORDER BY/LIMIT statements I was unaware of.

You can download my paper here.

My slides, like many talks just scratched the surface in the alloted. I’ve been working on additional reference material, a work in progress is available at …

All of the closing-social ice cream is gone and the conference center has quieted down to just folks putting equipment away. The "MySQL" wireless network is the last remaining indicator of the weeklong activities here in the Santa Clara Convention Center.

(Oh dear, I'm starting to sound like a reporter doing an intro to a technology segment).

It's been a jam-packed 4 days here in Santa Clara at the MySQL 2006 Users Conference. There has been so much that has happens since arriving on Sunday morning it seems more like a long, quickly moving blur.

For me this year was such a different experience from last year. The content was the same high quality as it has been in the past (this is my 3rd conference), but returning this year to familiar faces and having made connections with folks over the past year on planetmysql and other MySQL online gathering places has added a much …

I tried to upload my slides from the conference, but run into problems with a firewall somewhere, so they've had to wait for me to return home.

So, here we are: Using MySQL with PDO (PDF).

This was my first MySQL users conference, and it seemed to go well. Truth be told, I'm not a database fanatic (which is ironic considering my involvement with PDO), so I didn't find a lot of the material to my taste. I did learn a few things from Jim Winsteads embedded mysql talk (something I bet he'll be surprised to hear :) and also Hartmut Holzgraefe's mysqli talk. I also got to chat to Monty about the issues I mentioned and meet some new faces, including my Evil sysadmin, some old and some older faces (Hi …

In this article I’ll show you how to find the “next” and “previous” records (define these terms any way you like) in a set of records. My solution uses no subqueries or unions, so it works on old versions of MySQL, and returns both the next and the previous records in a single efficient query. Motivation I’m working on a project right now that requires me to use MySQL 3.

Closing keynote of MySQL UC 2006 is Milton Ngan from Weta Digital talking about using MySQL in making movies. I've heard Milton speak at OSCON in the past, some impressive movie stuff they do with CG.

Milton starts with a review of the movies that have come out of Weta and talks about the number of shots and number of processors they used to render those shots. King Kong had over 2000 shots and required 4,500 processors. Milton is doing this presentation on a Mac.

Weta now has over a petabyte of data on tapes for storing shots. Has 120 terrabytes worth of disks connected with 10Gb ethernet. Milton goes through some photos of the facilities, one photo has a row of cabinets that holds ~2,500 processors. Milton then goes through a number of snips from King Kong showing camera footage with CG layovers.

What uses MySQL at Weta? Production management. Storing details about …

Weta Digital, the company on Peter Jackson films
Heavenly Creatures (1994) nominated for
The Frighteners (1996)
in 1997, Peter Jackston started working on King Kong, but Universal canned it because there were a lot of monster and disaster movies.
Contact (1997) with Robert Zemeckis — the zero-gravity ride was done by Weta Digital
Then they did the Lord of the Rings trilogy (2001-3)
Van Helsing (2004) (just a few bits and pieces)
I, Robot (2004) nominated for best digital effects — technology for armies in Lord of the Rings was used here.
King Kong (2005) and trying to get what Peter Jackson wanted.

(make a chart!)
Size of a movie is based on a shot (camera doesn’t cut away). Visual effects movie typically had 500-1000 shots.

So I got to speak to MIlton Ngan right before his closing keynote. I don’t know where we got the idea that they (Weta Digital) ran Fedora, because all they’ve had are a bunch of Red Hat 9 machines as well as a few Debian. They seemingly are moving fully to Ubuntu real soon now. As always, sticking with MySQL.

Oh, and watch out for X-Men 3, out on May 19th…

Last session of the MySQL UC is Jim Starkey giving an introduction to the new Falcon storage engine. Jim is an icon in the database field, was the creator of MVCC and the BLOB data type. There's a can of Falcon beer for anyone who asks a good question.

What is Falcon

• transactional MySQL storage engine
• based on Netfrastructure database engine
• engine has been in mission critical apps for more than 4 years
• extended and integrated into MySQL

Falcon is NOT

• an InnoDB clone
• Firebird
• a Firebird clone
• a standalone database management management system
• Netfrastructure

Jim's been at this for a long time, there have been some changes since he wrote his first database at DEC:

• 
  
• Uni-processors to …

The slides for the talk I presented together with Zak on Application Clustering with MySQL & Squid is now available. The slides are in OpenDocument format so you need OpenOffice.org to view them. Any comments or suggestions welcome.
Update: slides are now also available in PDF format.