You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Patrick Linskey (JIRA)" <ji...@apache.org> on 2008/01/16 02:39:35 UTC

[jira] Created: (OPENJPA-487) Generated SUBSTRING SQL is ugly and inefficient

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: 1.0.1, 1.0.0, 0.9.7, 0.9.6, 0.9.0, 1.0.2, 1.1.0
            Reporter: Patrick Linskey
            Priority: Minor


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.
-
You can reply to this email to add a comment to the issue online.