[infinispan-issues] [JBoss JIRA] Updated: (ISPN-20) check whether locking in JDBC cache stores can be replaced with SELECT FOR UPDATE
Manik Surtani (JIRA)
jira-events at lists.jboss.org
Thu Jun 23 10:18:24 EDT 2011
[ https://issues.jboss.org/browse/ISPN-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manik Surtani updated ISPN-20:
------------------------------
Fix Version/s: 5.2.0.Final
(was: 5.1.0.BETA1)
(was: 5.1.0.Final)
> check whether locking in JDBC cache stores can be replaced with SELECT FOR UPDATE
> ---------------------------------------------------------------------------------
>
> Key: ISPN-20
> URL: https://issues.jboss.org/browse/ISPN-20
> Project: Infinispan
> Issue Type: Feature Request
> Components: Loaders and Stores, Locking and Concurrency
> Reporter: Mircea Markus
> Assignee: Mircea Markus
> Labels: hackathon
> Fix For: 5.1.0.BETA1, 5.1.0.Final
>
>
> Not sure whether the 'outside' locking (MVCC) can't be used so that we won't need locking code within cache stores
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list