On Feb 24, 2014, at 5:39 PM, Sanne Grinovero <sa...@infinispan.org> wrote:
> On 24 February 2014 16:51, Mircea Markus <mmar...@redhat.com> wrote: >> Just to recap the main reason for the JPA cache store is to be a replacement >> for the JDBCacheStore, nothing more than that. >> And it certainly has advantages compared with the JDBC Cache Stores: >> - JPA offers database independence/portability >> - doesn't put that many restrictions on the schema >> - it's easier write/read from an exiting database table > > Don't you dare hijacking my nice 2 years old thread :-D :-D > BTW why is this dicussion not public anymore? I missed the switch to > undercover. I don't know where it switched to private, make it public again ;) > > Cheers, > Sanne > >> >> >> >> On Feb 18, 2014, at 1:18 PM, Tristan Tarrant <tris...@infinispan.org> wrote: >> >>> I think that the CacheLoader/Store SPI should be enhanced with "schema" >>> information, whatever its source (JPA annotations, ProtoBuf, etc). >>> >>> A schema-aware store can then do what it pleases. >>> >>> Tristan >>> >>> On 18/02/2014 14:03, Emmanuel Bernard wrote: >>>> On Tue 2014-02-18 13:16, Adrian Nistor wrote: >>>>>> JPA cache store is a waste of time IMO :) >>>>> +1 :) >>>> My understanding is that the JPACacheStore discussion is revived because >>>> users want to map an existing databases, load the data in the grid and >>>> keep both synchronized. >>>> At least that's the use case I was told was needed to be covered. >>> >> >> Cheers, >> -- >> Mircea Markus >> Infinispan lead (www.infinispan.org) >> >> >> >> Cheers, -- Mircea Markus Infinispan lead (www.infinispan.org) _______________________________________________ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev