[ http://issues.apache.org/jira/browse/OPENJPA-63?page=all ]
Patrick Linskey updated OPENJPA-63: ----------------------------------- First, generally, I think that the patch is definitely an improvement. I agree that there are a bunch of things that we could (and probably should) parameterize. But as Igor points out, it's certainly better than what was already in OpenJPA. So we're moving in the right direction. Re: JDBC3: if we execute on this decision to drop support for JDK1.3, then the issue is moot. Also, this already is configurable at a coarse-grained level -- people can always set the forUpdateClause however they want, by setting the DBDictionary property to 'db2(ForUpdateClause="FOR UPDATE <MAGIC STRING HERE>"). > 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
