Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <8760125.328141285103734931.JavaMail.jira@thor>
Date: Tue, 21 Sep 2010 17:15:34 -0400 (EDT)
From: "Michael Dick (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Closed: (OPENJPA-1800) Duplicate column created for sybase
In-Reply-To: <7762799.235821284665852562.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Michael Dick closed OPENJPA-1800.
---------------------------------

    Resolution: Fixed

> Duplicate column created for sybase
> -----------------------------------
>
>                 Key: OPENJPA-1800
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1800
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>            Reporter: Michael Dick
>            Assignee: Michael Dick
>            Priority: Minor
>
> 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.