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

[Robert Stupp (JIRA)]

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

Robert Stupp commented on ISPN-20:
----------------------------------

You cannot assume, that all databases support transactions at all.
MySQL/MyISAM does not support transactions
MySQL/InnoDB supports transactions
MyQSL/NDB ???
SQL-Server supports transactions, but real row-level locking is a nightmare with it
Oracle - works - row level locking - has some "special" SQL that's great for this issue (read/write lock / exists-check) - don't remenmber the exact use
DB2 - works - but don't how locking is implemented (page / row ??)




> 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: Galder Zamarreño
>              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