use Perl

• Wow. (Score:1)

  by stu42j (6348)

  It is pretty interesting to see all those quirks together like that. Particularly the date handling.
  
  One of the things I actually like about MySQL is the idea of having different Storage Engines tuned for different purposes. I've often thought it would be interesting to some how use Postgres as a MySQL Storage Engine. I think Falcon will be close to that goal. I am looking forward to seeing how 6.0 turns out.
  • Been there, done that (Score:2)

    by merlyn (47)

    PostgreSQL as a MySQL storage engine [krow.net]. A bit like inserting an entire Hummer as the "engine" for your Kia.

    --
    

    • Randal L. Schwartz
    • Stonehenge
    • Re: (Score:1)

      by stu42j (6348)

      I think of it more like having a car with Variable displacement [wikipedia.org] where some cylinders in the engine can be disabled to save fuel, depending on the driving conditions.
      
      I can imagine, however, that the MySQL frontend may create limitations that prevent more advanced storage engines from being as useful.
    • Re: (Score:2)

      by vek (2312)

      PostgreSQL in MySQL? So that's how they get decent replication in PostgreSQL.
• Thanks! (Score:1)

  by ChrisDolan (2855)

  Excellent article, thank you!
  
  With regard to MySQL ignoring the REFERENCES field, I found it preferable to write my schema using REFERENCES and then convert it with SQL::Translator [cpan.org] to the FOREIGN KEY style like so:

  sqlt --from MySQL --to MySQL schema.sql > schema.mysql
• MySQL gotchas (Score:1)

  by Ianb (8211)

  A little dated, but the MySQL gotchas [sql-info.de] cover similar ground.
• longer than 2 years (Score:1)

  by perrin (4270)

  Saying MySQL 5 has only been available for 2 years is a bit questionable. It's been out in production for 2.5 and in (widely-used) beta for 3. It's standard on any modern Linux distro at this point.

  You seem to be implying that InnoDB tables are slower than MyISAM. For my workload it's been quite the opposite: InnoDB tables have been significantly faster.

  The right way to do ENUMs with enforcement is to use a lookup table with foreign keys, just like you would in many other databases. You made a really