[infinispan-issues] [JBoss JIRA] (ISPN-686) JdbcStringBasedCacheStore loads previous data from store before an insert

[Sanne Grinovero (JIRA)]

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

Sanne Grinovero commented on ISPN-686:
--------------------------------------

Hi Thomas,
"select ID" looks like a good compromise, but which DB are you using? As I mentioned above (years ago!) MySQL is able to deal with it in a single statement; Back in that time I was an external contributor, but shared my custom implementation using MySQL as a patch - should be in the mailing lists archive, but worth looking for only if you intend to MySQL.

I'm glad that someone finally volunteers on this :)
                
> JdbcStringBasedCacheStore loads previous data from store before an insert
> -------------------------------------------------------------------------
>
>                 Key: ISPN-686
>                 URL: https://issues.jboss.org/browse/ISPN-686
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Loaders and Stores
>    Affects Versions: 4.0.0.Final, 4.1.0.Final
>            Reporter: Sanne Grinovero
>            Assignee: Thomas Fromm
>             Fix For: 5.2.0.Final
>
>
> The JdbcStringBasedCacheStore implementation loads the previous data on an insert to find out if it should generate an UPDATE or INSERT statement, while it would perform much better to just verify if the primary key exists.
> On top of this, some databases provide ways to avoid the need to check at all, like MySQL's " INSERT ... ON DUPLICATE KEY UPDATE"
> [http://dev.mysql.com/doc/refman/5.0/en/insert-on-duplicate.html]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira