Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 350668

Summary: Discriminator Column is nullable
Product: z_Archived Reporter: Bernard Missing name <bht237>
Component: EclipselinkAssignee: Nobody - feel free to take it <nobody>
Status: NEW --- QA Contact:
Severity: normal    
Priority: P2 CC: tom.ware
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows Vista   
Whiteboard:
Attachments:
Description Flags
testcase none

Description Bernard Missing name CLA 2011-06-29 04:43:06 EDT 
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
Comment 1 Bernard Missing name CLA 2011-06-29 04:44:49 EDT 
Created attachment 198800 [details]
testcase
Comment 2 Tom Ware CLA 2011-07-08 11:09:49 EDT 
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.
Comment 3 Eclipse Webmaster CLA 2022-06-09 10:25:20 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink