[
https://issues.apache.org/jira/browse/OPENJPA-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
B.J. Reed updated OPENJPA-1308:
-------------------------------
Attachment: OPENJPA-1308-trunk.patch
OPENJPA-1308-1.2.x.patch
OPENJPA-1308-1.0.x.patch
Attached patches to be considered for inclusion to OpenJPA. No real
differences in the patches except that the 1.0.x patch includes a new test case
that wasn't already present in 1.0.x (the other 2 just modify the existing test
case).
For the most part, the change is that when UPPER or LOWER are used,
DB2Dictionary looks to see what the database column is defined as before doing
the cast. In this way, if the column is already a VARCHAR, then indexes would
still be used since no cast would be generated.
> shouldn't always use CAST with UPPER and LOWER for DB2
> ------------------------------------------------------
>
> Key: OPENJPA-1308
> URL: https://issues.apache.org/jira/browse/OPENJPA-1308
> Project: OpenJPA
> Issue Type: Improvement
> Components: sql
> Affects Versions: 1.0.3, 1.2.1, 2.0.0-M2
> Environment: DB2
> Reporter: B.J. Reed
> Priority: Minor
> Fix For: 2.0.0
>
> Attachments: OPENJPA-1308-1.0.x.patch, OPENJPA-1308-1.2.x.patch,
> OPENJPA-1308-trunk.patch
>
>
> Using DB2, when a user uses the UPPER or LOWER function, the field is
> automatically CAST to a varchar. It would be nice if OpenJPA were a little
> smarter and only used CAST when necessary. Using the CAST causes any indexes
> not to be used so performance won't be what it should.
> I saw some other DB2 functions that also are always CAST, so we may need to
> improve these also.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
