[infinispan-dev] chunking ability on the JDBC cacheloader

[Manik Surtani]

On 24 May 2011, at 12:18, Dan Berindei wrote:

> Ok, this probably won't be such a big problem with the redesigned JDBC
> cache store, but with the actual design you can't put a new value
> without first reading the old value, and you can't read the old value
> because the data has been truncated, so the only way to get out of
> this mess is to delete everything from that table from a SQL prompt.
> 
> If we can make it easier for the user to recover from a truncation
> then sure, just throw an exception on get, we don't want to handle
> every possible configuration problem in our code.

Once we have ISPN-701, we could potentially add some checks for specific vendors, but this would need to be optional/configurable.

--
Manik Surtani
manik at jboss.org
twitter.com/maniksurtani

Lead, Infinispan
http://www.infinispan.org