[
https://issues.apache.org/jira/browse/OPENJPA-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12890705#action_12890705
]
Martin Dirichs commented on OPENJPA-1651:
-----------------------------------------
What exactly is still holding back the resolution of this issue? I noticed that
the changes made for the precessor OPENJPA-1387 were rolled back. Now that a
newer version of Derby is used in the build process, it should be easy to fix
this. Or is it because of compatibility considerations? If so, a switch could
be added to support the old behaviour (which, as I see it, is really a bug, not
a feature).
> 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: Pinaki Poddar
> 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.
-
You can reply to this email to add a comment to the issue online.
