[
https://issues.apache.org/jira/browse/OPENJPA-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486065
]
Patrick Linskey commented on OPENJPA-197:
-
I'm a bit confused. Where did Hibernate and Toplink fail? The
[
https://issues.apache.org/jira/browse/OPENJPA-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486087
]
Jacek Laskowski commented on OPENJPA-197:
-
Hibernate and TopLink will fail once you get rid of the if
[
https://issues.apache.org/jira/browse/OPENJPA-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486089
]
Jacek Laskowski commented on OPENJPA-197:
-
As I'm unable to write to the dev mailing list I'm responding to
[
https://issues.apache.org/jira/browse/OPENJPA-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486091
]
Patrick Linskey commented on OPENJPA-197:
-
Note that there are significant performance impacts to doing
Hibernate and TopLink will fail once you get rid of the if
statement. It's because according to the spec (and my
understanding) merge should rise exception when the versioned
property is outdated.
No, the exception can be deferred until flush/commit. Read section
3.2.4.1.
Notice:
On Apr 2, 2007, at 11:18 AM, Abe White wrote:
The spec says in 3.2.4.1 p. 52: Any Version columns used by the
entity must be checked by the persistence runtime implementation
during the merge operation and/or at flush or commit time.
So, one could agree with Abe (the and/or is the key).
Ok.
[
https://issues.apache.org/jira/browse/OPENJPA-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486112
]
Jacek Laskowski commented on OPENJPA-197:
-
Please close the issue with WON'T FIX or alike due to the
