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.
  • Just choosing one over the other because of transactions is a dangerous game. They don't store the same, and they don't perform the same; even on the same non-transactional queries in some circumstances (count(*), multiple PKs, etc). For that matter, don't just assume your schema should be the same if you plan on using one vs. the other.

    This has always been a decent document to remind me that 'inno has transactions' isn't the only issue to think about:

    http://jpipes.com/presentations/mysql_perf_tuning.pdf [jpipes.com]
    • Oh, agree that 'inno has transactions' isn't the only thing to think about. The fact that Inno has transaction in itself isn't a reason to choice Inno.

      However, the reverse is true. The fact that MyISAM doesn't have transactions is almost always reason enough to not use MyISAM. The fact that it's hard to come up with a case where you can get away with MyISAM is (for me) reason enought to not even consider.