You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@openjpa.apache.org by "Donald Woods (JIRA)" <ji...@apache.org> on 2010/09/21 23:23:32 UTC

[jira] Updated: (OPENJPA-1800) Duplicate column created for sybase

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

Donald Woods updated OPENJPA-1800:
----------------------------------

        Fix Version/s: 2.1.0
    Affects Version/s: 2.0.0

> Duplicate column created for sybase
> -----------------------------------
>
>                 Key: OPENJPA-1800
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1800
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>    Affects Versions: 2.0.0
>            Reporter: Michael Dick
>            Assignee: Michael Dick
>            Priority: Minor
>             Fix For: 2.1.0
>
>
> In order to execute FOR UPDATE statements against Sybase we create a special column named UNQ_INDEX.
> Some of our schema tools cause the column to be inserted twice (in memory). I've seen this happen with testcases which use the DROP_TABLES constant - but any code that uses the following persistence property could see the same behavior :
> openjpa.jdbc.SynchronizeMappings=buildSchema(ForeignKeys=true,SchemaAction='drop,add')

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