[
https://issues.apache.org/jira/browse/OPENJPA-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680439#comment-13680439
]
Kevin Sutter commented on OPENJPA-673:
--------------------------------------
Hi Gurkan,
Which situation or scenario are you referring to? Reading through this JIRA,
there are several scenarios mentioned. One of the scenarios was resolved as a
"user error"... So, I'm a little confused on the specific issue you are
experiencing. As the previous posts, if you can provide a testcase that would
help greatly. And, since this JIRA has been open for a long time with no
"resolved versions", I'm wondering about what versions worked and what versions
didn't work. Since the original issue was opened in 2008, this was before JPA
2.0 was even developed. So, there's been a lot of code developed between then
and now...
Thanks for any clarifications you can provide.
Kevin
> Entity using Generated Value for primary key and a Version field and no
> DetachedStae fails to merge
> ----------------------------------------------------------------------------------------------------
>
> Key: OPENJPA-673
> URL: https://issues.apache.org/jira/browse/OPENJPA-673
> Project: OpenJPA
> Issue Type: Bug
> Reporter: Pinaki Poddar
>
> Entities using GeneratedValue for primary key, a version field an dno
> detached state fails to merge.
> The issue lies with identifying :"what makes a new instance?"
> It is not obvious why VersionAttachStrategy does not use version field to
> detect newness. Instead it depends on detached state which is obviously null
> for instances not using a Detached State.
> Can someone shade some light on why VersionAttachStrategy ignores version
> field to detect newness?
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
