[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-3671) The revision type field is not persisted when setting a custom revision type field name throught the properties

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3671?page=c... ] Mark Derricutt commented on HHH-3671: ------------------------------------- Hey Adam, I just spent some time tracing the code and seeing if I could spot it, and I have - or at least I believe so. And I believe its just a foobar on my own part (or more, our schema, and ensuing confusion). This all relates to our use of subclassed entities, I have two tables: party_versions, and person_versions. party_versions is for the super class and has _revision and _revision_type, person_versions ALSO has _revision -AND- _revision_type. My guess is this second _revision_type column is actually redundant, which is why I never seeing it being inserted. Looking at my party_versions table I see that _revision_type is populated properly. So it looks like I my schema file (generated manually) included several redundant columns. Can you confirm this behaviour/confusion is correct? If so - feel free to close this ticket :) -- 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