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.
  • by Ovid (2709) on 2010.04.09 2:15 (#71875) Homepage Journal

    What forced the switch from Postgres? Even worse, why MyISAM? I assume there's a compelling story in there somewhere :)

    • It seems to me if one were to have good reason to pick MySQL, then it would necessarily be for MyISAM. That engine is at least compelling insofar as it is essentially a NoSQL database with an SQL frontend. For mostly-read workloads it’s an interesting option.

      In contrast, InnoDB is just a crippled wannabe regular transactional RDBMS. There are far better choices if you need one of those. InnoDB only ever makes sense to use when you are stuck with MySQL as an a priori constraint.

    • Because they didn't want to support another database. They are using Oracle and MySQL, and that's it. I was lobbying for Postgres, but in the end the corporate policy won. I can see their point, but it was still painful...