You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Albert Lee (Closed) (JIRA)" <ji...@apache.org> on 2012/02/02 17:24:51 UTC
[jira] [Closed] (OPENJPA-487) Generated SUBSTRING SQL is ugly and
inefficient
[ https://issues.apache.org/jira/browse/OPENJPA-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Albert Lee closed OPENJPA-487.
------------------------------
Close issue in preparation for 2.2.0 release.
> Generated SUBSTRING SQL is ugly and inefficient
> -----------------------------------------------
>
> Key: OPENJPA-487
> URL: https://issues.apache.org/jira/browse/OPENJPA-487
> Project: OpenJPA
> Issue Type: Improvement
> Components: sql
> Affects Versions: 0.9.0, 0.9.6, 0.9.7, 1.0.0, 1.0.1, 1.0.2, 1.1.0
> Reporter: Patrick Linskey
> Assignee: Milosz Tylenda
> Priority: Minor
> Fix For: 2.2.0
>
> Attachments: handle_params_in_group_by.patch
>
>
> When performing a JPQL query with a SUBSTRING clause, OpenJPA converts from one-based index + length parameters to zero-based index + end index for internal handling, and then re-converts back to one-based + length when generating SQL. This conversion is entirely performed in query values, so the generated SQL has a lot of math in it. This extra math is never necessary.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira