MySQLDialect vs. MySQLInnoDBDialect
I've used Hibernate's MySQLDialect ever since I started using Hibernate and MySQL. However, I noticed with Hibernate 3 there's a couple of new MySQL Dialects in town: MySQLInnoDBDialect and MySQLMyISAMDialect. Using MySQLDialect still seems to work fine for me - and it handles transaction rollbacks when I'm using InnoDB types.
What's the point of these fine-grained dialects? Should they be used when possible, or does MySQLDialect default to one of these based on MySQL metadata? IMO, Hibernate's javadocs could stand to have a little more "doc" action. Maybe I'm just not looking in the right place for the answer to this question.
Posted by Nicolas Cornaglia on October 19, 2005 at 09:23 AM MDT #
Posted by 188.8.131.52 on October 19, 2005 at 09:53 AM MDT #
Posted by Matt Raible on October 19, 2005 at 03:46 PM MDT #
Posted by Thomas Risberg on October 19, 2005 at 07:39 PM MDT #
Posted by John Fereira on October 23, 2005 at 07:22 AM MDT #