Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Date: Wed, 23 Mar 2011 14:22:06 +0000 (UTC)
From: "Michael Dick (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Message-ID: 
 <1970305211.6064.1300890126071.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (OPENJPA-1665) Problems when using auto
 incrementing colums that start at zero
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/OPENJPA-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Dick updated OPENJPA-1665:
----------------------------------

    Fix Version/s: 2.0.2
                   1.3.0
                   1.2.3

> Problems when using auto incrementing colums that start at zero 
> ----------------------------------------------------------------
>
>                 Key: OPENJPA-1665
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1665
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Rick Curtis
>            Assignee: Rick Curtis
>             Fix For: 1.2.3, 1.3.0, 2.0.2, 2.1.0
>
>
> This issue was reported on the users mailing list[1].
> The issue is that it is possible when using auto generated ids that there is a current entity in the persistence context that has an id of zero, and by default when a new entity is created it also has an id of zero. When persisting the second entity, OpenJPA incorrectly detects that there are multiple entities with the same id in the context even though the new id doesn't have an id from the database yet.
> [1]http://openjpa.208410.n2.nabble.com/An-object-of-type-src-StatusUpdate-with-oid-0-already-exists-in-this-context-another-cannot-be-persi-td5030272.html#a5030272

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira