You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Patrick Linskey (JIRA)" <ji...@apache.org> on 2008/04/23 00:03:21 UTC

[jira] Commented: (OPENJPA-567) @OrderColumn generates duplicate order numbers.

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

Patrick Linskey commented on OPENJPA-567:
-----------------------------------------

Patch looks good. I'm running a remote test against it now; it should submit to the 1.1.x branch shortly.

I had been curious about backward-compatibility with existing data sets; Srinivas points out that this isn't an issue since the result set will never be empty in the case that there is data, and so the existing data will be read.

> @OrderColumn generates duplicate order numbers.
> -----------------------------------------------
>
>                 Key: OPENJPA-567
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-567
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>    Affects Versions: 1.0.2
>            Reporter: Vikram Bhatia
>            Priority: Minor
>         Attachments: OrderColumnTest.zip, proposed-soln.patch
>
>
> @OrderColumn generates and inserts duplicate entries. This is not always the issue, but only for first number, and it starts at 1 instead of 0. The problem is in class StoreCollectionFieldStrategy.load() method where variable seq needs to be initialized with -1.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.