| Summary: | Ignore case on field comparisons for PostgreSQLPlatform | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Rodrigo Hjort <rodrigo.hjort> |
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | christopher.delahunt, tom.ware |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Rodrigo Hjort
Actually it is JPA 1.0's EntityManager.createNamedQuery(String) method along with the annotation below:
@NamedNativeQuery(
name = "newestAuctions",
query = "select * from auctions where status = ?1 order by creation desc limit ?2",
resultClass = Auction.class
)
Setting target and priority. For information about the meanings of these fields see: http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines Fix 299926 in 2.1 added a "eclipselink.jpa.uppercase-column-names" property to enable case sensitivity without having to call platform code, but the default was still false. The this was changed to true as of EclipseLink 2.5 with the fix for 321649, so marking this as a duplicate. *** This bug has been marked as a duplicate of bug 321649 *** The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |