I'm not sure if I understood him completely either; I think he wants to use OGM, but making sure the Infinispan cacheloader still stores in a relational database using it's relational mapping (what you identified as #1); Assuming OGM is managing both worlds, an OGM CacheLoader might be able to "recognize" it's very own tuples format and re-map it to the relational tables. This second step phase could then take advantage of Infinispan's async storage, so OGM would indeed write to both the grid and the database, but not necessarily at the same time, or the database might even occasionally slowdown or fail without consequences to the application.
--Sanne On 30 September 2011 09:57, Emmanuel Bernard <emman...@hibernate.org> wrote: > I am a bit confused, > Does the guy want to have an ISPN cache store that store the data in a proper > relational model? > Or does he want Hibernate OGM to store in both ISPN and the relational > database in parallel? > > I think he is talking about 1, which I admit I haven't thought about (ie > reusing JPA's metadata to have the right relational model. It's an > interesting idea to explore. > > On 29 sept. 2011, at 18:52, Sanne Grinovero wrote: > >> Hi, >> there is this thread on the OGM forums, for which I think the last >> post makes an interesting read: >> >> https://forum.hibernate.org/viewtopic.php?p=2449117#p2449117 >> >> people want the flexibility of the "grid", but still permanently store >> the important stuff in their trusted relational database. >> >> I agree with the user in saying that this would certainly make OGM >> even more interesting, something to consider in the design as a long >> term plan. >> In addition, it would provide a reliable way to perform relational queries :) >> >> Sanne > > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
