[hibernate-issues] [Hibernate-JIRA] Resolved: (HHH-2242) Consider Allowing Optimistic Lock Strategies other than 'Version' with joined-subclass

[Steve Ebersole (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2242?page=all ]
     
Steve Ebersole resolved HHH-2242:
---------------------------------

    Fix Version: 3.2.2
     Resolution: Fixed
      Assign To: Steve Ebersole

In theory, "none" should be fine.  Conceptually a joined-subclass would support optimistic-locking="none|version" (please note that version really means version or timestamp).

However, the two property-based optimisitc locking schemes (all & dirty) are conceptually not correct with joined-subclasses.  We could relax that if we enforced that all properties actually used in optimistic locking occurred in the "base table".  But thats not worth the effort.

Not sure if you realize, though, but optimisitc-locking="none" is exactly the same thing as optimisitc-locking="version" (or specifying nothing for this attribute) and then *not* defining a <version/> or <timetsamp/>...

Anyway, its trivial to change it.  So I went ahead and changed the code to explicitly allow optimisitc-locking="none" on joined-subclass.

trunk / 3.2

> Consider Allowing Optimistic Lock Strategies other than 'Version' with joined-subclass
> --------------------------------------------------------------------------------------
>
>          Key: HHH-2242
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2242
>      Project: Hibernate3
>         Type: Improvement

>   Components: documentation, core
>     Versions: 3.2.0.ga
>     Reporter: Phillip Tornroth
>     Assignee: Steve Ebersole
>     Priority: Minor
>      Fix For: 3.2.2

>
>
> The JoinedSubclassEntityPersister class explicitly disallows mapping joined-subclasses whenever an optimistic locking strategy of other than 'version' is used. It would be very useful to choose an optimistic locking strategy independent of an inheritance mapping strategy. In my case, I'm using 'none' for legacy reasons. If there's a good reason for continuing to enforce this constraint, it would be very helpful to document it in the hibernate reference. 
> Thanks in advance...

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira