You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "sreenath bhasker (Jira)" <ji...@apache.org> on 2019/10/19 17:45:00 UTC

[jira] [Commented] (OPENJPA-673) Entity using Generated Value for primary key and a Version field and no DetachedStae fails to merge

    [ https://issues.apache.org/jira/browse/OPENJPA-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16955229#comment-16955229 ] 

sreenath bhasker commented on OPENJPA-673:
------------------------------------------

Am facing the same issue in openjpa 2.4.3 version,is there a fixor workaround  for this. Please help

> 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
>            Priority: Major
>
> 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 was sent by Atlassian Jira
(v8.3.4#803005)