Exactly.
Obviously in the case of a JPA cache store, the V would be an @Entity and
therefore "automapped" by the persistence provider. For Cassandra this would
have to be explicitly processed by a Value to Store mapper (which could come
useful also with the plain JDBC store).
Tristan
On Fri, Dec 3, 2010 at 11:33, Manik Surtani <manik(a)jboss.org> wrote:
Tristan,
We do have an open JIRA for a JPA cache store over a RDBMS, which would map
entities on to columns. Are you suggesting something similar?
Cheers
Manik
On 3 Dec 2010, at 07:58, Tristan Tarrant wrote:
> Dear all,
>
> after adding the key mapping functionality to the Cassandra cache store,
I was thinking that it would be nice to have a similar feature for mapping
values to Cassandra's columns and column families (I don't know if these
concepts are familiar to you, but they roughly translate to columns in a
relational database). This means that instead of putting a binary blob into
the store, the data would be mapped in a more natural format. This could
also come in useful for the JDBC store.
> This would obviously be done as part of 5.x.
>
> Ideas & suggestions ?
>
> Tristan
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Manik Surtani
manik(a)jboss.org
Lead, Infinispan
Lead, JBoss Cache
http://www.infinispan.org
http://www.jbosscache.org
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev