[infinispan-issues] [JBoss JIRA] (ISPN-3680) Inconsistent way to use the column id in the JdbcBinaryCacheStore

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on ISPN-3680:
-----------------------------------------------

Paul Gier <pgier at redhat.com> changed the Status of [bug 1087205|https://bugzilla.redhat.com/show_bug.cgi?id=1087205] from MODIFIED to ON_QA

> Inconsistent way to use the column id in the JdbcBinaryCacheStore
> -----------------------------------------------------------------
>
>                 Key: ISPN-3680
>                 URL: https://issues.jboss.org/browse/ISPN-3680
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Loaders and Stores
>    Affects Versions: 5.2.7.Final, 5.3.0.Final, 6.0.0.CR1
>            Reporter: Nicolas Filotto
>            Assignee: Mircea Markus
>             Fix For: 7.0.0.Alpha4, 5.2.9.Final
>
>
> I met some issues with (at least) H2 and JdbcBinaryCacheStore that prevent to modify a value in the cache store which is quite annoying. After a deeper look, I realized that it was due to the method {{JdbcBinaryCacheStore.loadBucket(Integer keyHashCode)}} that uses {{setInt}} instead of {{setString}} like in updateBucket and insertBucket to set the id as parameter to the query. With HSQLDB and MySQL, it works normally but with H2, the result of the query is always empty so it always tries to add a new entry which of course fails because of the integrity constraint on the primary key (aka the id).



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)