]
Steve Ebersole updated HHH-2806:
--------------------------------
Priority: Major (was: Critical)
Not strictly true. The table type will be whatever type you specified as the default for
that database. You really use MyISAM as your default table type?!?
Enhanced TableGenerator is not cluster-safe on MySQL (does not use
correct table type)
--------------------------------------------------------------------------------------
Key: HHH-2806
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2806
Project: Hibernate3
Issue Type: Bug
Components: core
Affects Versions: 3.2.5
Environment: Mac OS X 10.4.10 (Intel), Java 1.5.0_07, MySQL 5.0.24a
Reporter: Matt Solnit
The org.hibernate.id.enanced.TableGenerator.sqlCreateStrings() method does not include a
call to Dialect.getTableTypeString(). This means that on MySQL, it will +always+ use
MyISAM, even if the Hibernate dialect is "MySQL5InnoDBDialect".
The result is that the FOR UPDATE lock has no effect, and the generator is not
cluster-safe. In other words, multiple Hibernate applications can receive the same ID and
get a primary key violation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: