openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Dirichs (JIRA)" <>
Subject [jira] Commented: (OPENJPA-1651) Unique colums automatically defined as non-nullable (part 2)
Date Wed, 21 Jul 2010 12:21:49 GMT


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:
>             Project: OpenJPA
>          Issue Type: Bug
>            Reporter: Mark Struberg
>            Assignee: Pinaki Poddar
>         Attachments:
> 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.

View raw message