openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Curtis (JIRA)" <>
Subject [jira] [Resolved] (OPENJPA-2162) Avoid delimited identifier processing if it's not required by application
Date Fri, 25 May 2012 14:32:24 GMT


Rick Curtis resolved OPENJPA-2162.

       Resolution: Fixed
    Fix Version/s: 2.2.1

Merged changes from trunk to 2.2.x.
> Avoid delimited identifier processing if it's not required by application
> -------------------------------------------------------------------------
>                 Key: OPENJPA-2162
>                 URL:
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: jdbc, performance, sql
>    Affects Versions: 2.3.0, 2.2.1
>            Reporter: Kevin Sutter
>            Assignee: Kevin Sutter
>             Fix For: 2.3.0, 2.2.1
> Supporting delimited identifiers causes some unnecessary overhead if the application
and associated database doesn't use them or support them.  This change will surface the DBDictionary
property supportsDelimitedIdentifiers.  Currently, this property gets set by querying the
database to see if the database supports this capability.  With this change, we will first
check if this property has been explicitly set.  If explicitly set, then we'll use that value.
 Otherwise, we will default back to querying the database to determine whether to support
delimited identifiers or not.
> Here's an example of the property to set to turn off the delimited identifier support:
> <property name="openjpa.jdbc.DBDictionary" value="db2(SupportsDelimitedIdentifiers=false)"/>

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message