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

Bug 334793

Summary: CHAR(2) column on Oracle not handled correctly (data truncated)
Product: z_Archived Reporter: Mike Norman <michael.norman>
Component: EclipselinkAssignee: Nobody - feel free to take it <nobody>
Status: RESOLVED FIXED QA Contact:
Severity: critical    
Priority: P2 CC: eclipselink.dbws-inbox
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:
Attachments:
Description Flags
set attributeClassification to String for CHAR(nn) fields none

Description Mike Norman CLA 2011-01-19 10:26:35 EST 
{NB - an internal Oracle tester found this problem}

When parsing the JDBC metadata for a table column's type, a CHAR(2)
column (or any CHAR(NN) field) is not handled correctly. The
mappings attributeClassification is set to java.lang.Character which
leads to all values being truncated to a single character.

The proper attributeClassification is java.lang.String
Comment 1 Mike Norman CLA 2011-01-19 11:27:07 EST 
Created attachment 187127 [details]
set attributeClassification to String for CHAR(nn) fields
Comment 2 Mike Norman CLA 2011-01-19 11:44:54 EST 
fix in SVN revision: 8848
Comment 3 Eclipse Webmaster CLA 2022-06-09 10:14:02 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
Comment 4 Eclipse Webmaster CLA 2022-06-09 10:35:34 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink