[infinispan-issues] [JBoss JIRA] Commented: (ISPN-20) check whether locking in JDBC cache stores can be replaced with SELECT FOR UPDATE

[Manik Surtani (JIRA)]

    [ https://jira.jboss.org/jira/browse/ISPN-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12502259#action_12502259 ] 

Manik Surtani commented on ISPN-20:
-----------------------------------

Either SELECT FOR UPDATE or we could use INSERT OR UPDATE.  Then we don't need to read before we write.  

MySQL uses INSERT ... ON DUPLICATE KEY UPDATE ...

http://dev.mysql.com/doc/refman/5.1/en/insert.html

But this would need to be db independent ... 

> check whether locking in JDBC cache stores can be replaced with SELECT FOR UPDATE
> ---------------------------------------------------------------------------------
>
>                 Key: ISPN-20
>                 URL: https://jira.jboss.org/jira/browse/ISPN-20
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Loaders and Stores, Locking and Concurrency
>            Reporter: Mircea Markus
>            Assignee: Mircea Markus
>             Fix For: 4.1.0.BETA1, 4.1.0.GA
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira