[OPENJPA-2162] Avoid delimited identifier processing if it's not required by application

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.1, 2.3.0
• Fix Version/s: 2.2.1, 2.3.0
• Component/s: jdbc, performance, sql
• Assignee: Kevin W. Sutter
• Reporter: Kevin W. Sutter
• Created: 27/Mar/12 20:31
• Updated: 09/Oct/12 18:40
• Resolved: 25/May/12 14:31

Description

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)"/>