[
https://issues.apache.org/jira/browse/OPENJPA-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13168454#comment-13168454
]
Mark Struberg commented on OPENJPA-1651:
----------------------------------------
Nope sorry, I reverted it. But if you point me to how I can provide a test
which only runs against MySQL, Oracle, etc then I can redo my work pretty
easily (~2hrs of work). I basically did put the logic I had in the attached
openjpa-test.zip and moved it to openjpa-persistence-jdbc unique tests.
I also duplicated the Entity to make sure that both @Column(unique=true) and
@UniqueColumns on the whole table are tested.
> Unique colums automatically defined as non-nullable (part 2)
> ------------------------------------------------------------
>
> Key: OPENJPA-1651
> URL: https://issues.apache.org/jira/browse/OPENJPA-1651
> Project: OpenJPA
> Issue Type: Bug
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 2.2.0
>
> Attachments: openjpa-test.zip
>
>
> Continuing the discussion from OPENJPA-1387. The original issue was closed
> and marked as shipped in OpenJPA 2.0.0 (one of the betas) - it should not
> appear in 2.0.1 as well - thus the need for a new issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
