[ http://issues.apache.org/jira/browse/OPENJPA-63?page=comments#action_12448584 ] Kevin Sutter commented on OPENJPA-63: -------------------------------------
Thanks, Igor, for your comments. I agree with you (and Patrick) that a general case solution is better than nothing at this point. If you can provide an updated patch, I will take another look at it and get it committed. Thanks. One question though... In your first bullet reply, you said that you would change the lock clause to "..UPDATE LOCKS". But, in your "solid generic clause" reply, you said "..EXCLUSIVE LOCKS". I'm pretty sure that was just a copy-and-paste error, but I wanted to double check that you were going to use "..UPDATE LOCKS". Thanks, 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
