You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Kevin Sutter (JIRA)" <ji...@apache.org> on 2006/10/24 15:47:18 UTC
[jira] Commented: (OPENJPA-63) Better pessimistic lock support for
DB2 v8.2+
[ http://issues.apache.org/jira/browse/OPENJPA-63?page=comments#action_12444315 ]
Kevin Sutter commented on OPENJPA-63:
-------------------------------------
I was just taking a look at Igor's patch and it looks rather straight-forward. But, my general question is how do we (OpenJPA) want to support multiple versions of a given DB dictionary? Do we want a single dictionary and then do the version checks at runtime as Igor as presented? Or, do we want individual dictionaries for the versions that are supported and then load the right one based on the configuration? It seems like we could go either way. Is there a preference or a precedence that we should stick to?
Kevin
> Better pessimistic lock support for DB2 v8.2+
> ---------------------------------------------
>
> Key: OPENJPA-63
> URL: http://issues.apache.org/jira/browse/OPENJPA-63
> Project: OpenJPA
> Issue Type: Improvement
> Components: jdbc
> Environment: IBM DB2 UDB v8.2 or later
> Reporter: Igor Fedorenko
> Attachments: db2-selectForUpdate.patch
>
>
> There is new SELECT "FOR READ ONLY WITH RS USE AND KEEP EXCLUSIVE LOCKS" syntax in DB2 v8.2 and later that can be used to implement pessimistic locks for selects with multiple from tables, subselects, inner/outer joins and so forth. I'll attach simple patch shortly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira