[
https://issues.apache.org/jira/browse/OPENJPA-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OPENJPA-1651.
------------------------------------
Resolution: Fixed
Fix Version/s: 2.2.0
Assignee: Mark Struberg (was: Pinaki Poddar)
I verified the behaviour with MySQL today and it works now with my test
project. I also tried to implement unit tests in openjpa-persistence-jdbc, but
that doesn't work because derby (which is used in the unit tests) doesn't
support NOT NULL values for UNIQUE indexes.
See the following discussion on the derby user list:
http://mail-archives.apache.org/mod_mbox/db-derby-dev/200511.mbox/%[email protected]%3E
> 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
