Community
Participate
Working Groups
Build Identifier: 2.3.0.v20110604-r9504 During some transition scenario that I cannot reproduce, I found that EclipseLink creates the default discriminator column "DTYPE" as nullable. I cannot imagine that there is a case where an entity would be persisted that contains null in this value. In my case, it prevented discovery of the scenario in which one such entity with null in "DTYPE" was created - it was creating problems later. The attached testcase is a NetBeans project that needs some configuration of its libraries. Reproducible: Always Steps to Reproduce: 1. Extract the attached testcase and open in NetBeans 2. Configure persistence.xml 3. Configure libraries 4. Run JUnit test - should create table 5. Inspect table layout - column "DTYPE" should NOT be nullable
Created attachment 198800 [details] testcase
Setting target and priority. See the following page for the meanings of these fields: http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines Community: Please vote for this bug if it is important to you. Votes are one of the main criteria we use to determine which bugs to fix next.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink