PostgreSQL 8.4 will have a ROW_NUMBER() windowing function so this little hack will
hopefully be unnecessary when 8.4 is in production.
Getting back to this exercise, this was actually inspired by Hubert's recent article Tips N’ Tricks - setting field based on order. Why this inspired me, I guess because it stirred
up memories about the often forgotten utility of arrays in PostgreSQL and I thought it would answer a question that was haunting
me - How do I assign sequential numbers to a list?. The article just didn't quite read the way I expected it to and actually
was answering another question I cared much less about, but it did get the
juices flowing. So without much further ado.
MySQL is turning out to be one big soap opera as far as I can tell and as Bruce Momjian has mentioned.
Lets go over some of the interesting episodes of this saga:
First Sun buys MySQL
Falcon storage engine creator Jim Starkey leaves MySQL/Sun
Brian Aker heads Drizzle which is a fork of MySQL that hopes to be a stream-lined
implementation of MySQL that leaves out all that nonsense we don't need such as views and stored procs
and targeting it self for running on the cloud, optimizing for massive concurrency, and ease of install. I presume Brian still works for MySQL/Sun though.
I'm not sure what all these things say about the stability of the MySQL core. I mean should I stick with MySQL 5 or run for the Drizzle, but I think I'll stick with PostgreSQL
where ever I can. PostgreSQL may not be quite as interesting from a soap opera perspective,
but it seems a tad bit more dependable and I really like my views and stored functions.