[
https://issues.apache.org/jira/browse/OPENJPA-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated OPENJPA-964:
---------------------------------
Attachment: OPENJPA-964-informix.patch
Patch <OPENJPA-964-informix.patch> includes InformixDictionary updates for
query timeout exception handling -
1) now properly sets VENDOR_IBM if the JCC driver is used
2) removes supportsQueryTimeout = false so we can set and catch timeouts
3) adds matchErrorState() to map a SQL Code = -213 to a QueryTimeoutException
This patch prereqs the <OPENJPA-964-common.patch> patch, which sets the SQL
State = IX000 to check.
> Finish updating sql-error-state- codes.xml for query timeout support on other
> DBs
> ---------------------------------------------------------------------------------
>
> Key: OPENJPA-964
> URL: https://issues.apache.org/jira/browse/OPENJPA-964
> Project: OpenJPA
> Issue Type: Sub-task
> Components: query
> Affects Versions: 2.0.0
> Reporter: Donald Woods
> Assignee: Donald Woods
> Fix For: 2.0.0
>
> Attachments: OPENJPA-964-common.patch, OPENJPA-964-db2.patch,
> OPENJPA-964-informix.patch, OPENJPA-964-mssql.patch, OPENJPA-964-oracle.patch
>
>
> Need to add any SQLStatus codes for query timeouts to sql-error-state-
> codes.xml and handle setting isRecoverable/isFatal in each DBDictionary
> subclass for other supported DBs besides Derby and DB2.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
