Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • 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.
  • 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
  • A little dated, but the MySQL gotchas [sql-info.de] cover similar ground.
  • 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