Bug 316045 - eclipselink.jpa.uppercase-column-names is causing field names to be uppercase in generated SQL
Summary: eclipselink.jpa.uppercase-column-names is causing field names to be uppercase...
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Chris Delahunt CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 319784 (view as bug list)
Depends on:
Blocks: 294267
  Show dependency tree
 
Reported: 2010-06-07 14:47 EDT by Chris Delahunt CLA
Modified: 2022-06-09 10:06 EDT (History)
1 user (show)

See Also:

Attachments
proposed fix, test cases to come later (51.79 KB, patch)
2010-06-15 15:29 EDT, Chris Delahunt CLA 		no flags Details | Diff
proposed JPA fix with test refactoring (52.24 KB, patch)
2010-07-22 09:09 EDT, Chris Delahunt CLA 		no flags Details | Diff
Show Obsolete (1) View All 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 2010-06-07 14:47:55 EDT 
While the name of the property eclipselink.jpa.uppercase-column-names suggest fields are to be uppercase the intent of the flag is to solve the case sensitivity issue within EclipseLink, by using uppercase field names only during comparisons.  When it is set user defined columns are being passed in as uppercase in the generated SQL as well. ie:
@Column(name="MixedCaseName")
-> SQL: "SELECT t0.MIXEDCASENAME FROM TABLE t0"

This causes errors on case sensitive database where the field is defined as "MixedCaseName".  As this will break applications or require them to change a property to get around it, this issue is preventing the eclipselink.jpa.uppercase-column-names property from defaulting to true, blocking 294267.
Comment 1 Chris Delahunt CLA 2010-06-15 15:29:00 EDT 
Created attachment 171982 [details]
proposed fix, test cases to come later
Comment 2 Chris Delahunt CLA 2010-07-22 09:09:33 EDT 
Created attachment 174965 [details]
proposed JPA fix with test refactoring
Comment 3 Chris Delahunt CLA 2010-07-26 10:43:23 EDT 
Fix checked into 2.1.1 and main
Comment 4 Chris Delahunt CLA 2010-08-25 12:18:56 EDT 
*** Bug 319784 has been marked as a duplicate of this bug. ***
Comment 5 David Green CLA 2010-08-26 13:20:23 EDT 
is there a binary download available with this fix?
Comment 6 Chris Delahunt CLA 2010-08-26 13:26:14 EDT 
Downloads are available from 
http://www.eclipse.org/eclipselink/downloads/index.php
You can get 2.1.1 or 2.2 with the fix from either the nightly builds or a milestone built after the posting mentioning it was checked in.
Comment 7 Eclipse Webmaster CLA 2022-06-09 10:06:14 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink