openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Chauvet (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OPENJPA-2361) BuildSchema/DDL : removing constraints unique/nullable has no effect.
Date Fri, 29 Mar 2013 15:31:31 GMT

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

Guillaume Chauvet updated OPENJPA-2361:
---------------------------------------

    Attachment: OPENJPA-2361.zip
    
> BuildSchema/DDL : removing constraints unique/nullable has no effect.
> ---------------------------------------------------------------------
>
>                 Key: OPENJPA-2361
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2361
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 2.2.0, 2.2.1
>         Environment: Windows 7 64 bits, JRE 1.6.0_43, Derby 10.8.2.2
>            Reporter: Guillaume Chauvet
>         Attachments: OPENJPA-2361.zip
>
>
> We have noticed during the database upgrade by OpenJPA that an annotated field with @Column(unique=true)
in our previous DB model  - annotated now @Column(unique=false) - doesn't remove the old unique
constraint. There is the same behaviour with @Column(nullable=true/false).
> Current workaround: we drop the constraint with a native SQL request.
> Attached please find two bundled unitary testsuites that reproduce the problem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message