This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 367887 - handle catalogue and schema more consistently
Summary: handle catalogue and schema more consistently
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 333739
  Show dependency tree
 
Reported: 2012-01-04 15:05 EST by Chris Delahunt CLA
Modified: 2022-06-09 10:04 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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