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

Bug 367887

Summary: handle catalogue and schema more consistently
Product: z_Archived Reporter: Chris Delahunt <christopher.delahunt>
Component: EclipselinkAssignee: Project Inbox <eclipselink.foundation-inbox>
Status: NEW --- QA Contact:
Severity: enhancement    
Priority: P3 CC: peter
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:
Bug Depends on:    
Bug Blocks: 333739    

Description Chris Delahunt CLA 2012-01-04 15:05:28 EST 
JPA allows defining the Catalogue and Schema independently of the table name, and so they can be delimited separately.  The tableQualifier in DatabaseTable needs to be broken up into catalogue and schema, and code created to delimit each seperately.  This same work needs to be factored into the DDL generation code.  

For DDL generation, delimiting is ignored completely on the catalogue and schema.  Ie, if delimiting is set, it will use catalogue.schema."TABLE" to create the table, but SQL that would be generated at runtime would be "catalogue.schema"."TABLE" in many cases.  EclipseLink core is inconsitent in using the getTableQualifierDelimited or getTableQualifier.
Comment 1 Chris Delahunt CLA 2012-01-11 10:29:14 EST 
This is related to 
Bug 333739 - identifiers are not delimited in all cases despite <delimited-identifiers />
Comment 2 Eclipse Webmaster CLA 2022-06-09 10:04:27 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink