[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3454?page=c...
]
Steve Ebersole commented on HHH-3454:
-------------------------------------
I have tests showing this works w/o annotations, and just looked at the code for how
annotations deals with this and I do not see any problems with it. Please make *sure* you
are using the Hibernate Core version you think you are using
Allow enhanced.TableGenerator to segment itself per entity as
default
---------------------------------------------------------------------
Key: HHH-3454
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3454
Project: Hibernate Core
Issue Type: Improvement
Components: core
Affects Versions: 3.3.0.SP1
Reporter: Steve Ebersole
Assignee: Steve Ebersole
Fix For: 3.2.x, 3.3.1, 3.4
Currently TableGenerator use a static string ("default" ) for its default
segment column name. The implication is that all TableGenerators defined without
specifying a segment value explicitly ended up using the same row.
Where this cam up was in the case of annotations where the generator is attached to a
base entity class.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira