Forgive my saying so, but isn't this a business layer level issue? And shouldn't Nhibernate be used just to persist data?
That being said (and it's just a thought) I don't see any reason why you couldn't turn flushing off (presuming that no other data access is required), and then manually flush the data when required? (Someone else will probably have a better solution...) I don't think you'd need the hibernate cache for this, but without such things as your environment (web? desktop?), I can't really make any other suggestions On Thursday, June 7, 2012 1:30:41 PM UTC+1, Sudripto wrote: > > We have a modeller (which is basically an IDE built in VS 2010 and C#) > which needs to open a model from a XML. A Model is a group of Entities > and Sub Entities or in Other words a Tree Graph of Objects. The > intention is to then allow all the modelling functions and change the > objects properties and values, add more values, delete a few old > values and then save the XML in some cache, all doing it correctly > without relying on the DB to validate the data. > Think of a scenario similar to Dataset in ADO.net or ClientDataSet in > Delphi. Everything done at client side. Then when there is connection > to the database at a later stage the Data will be persisted. We need a > similar scenario. Save the Object graph in Cache and then synchronize > with the Database at a later stage. > > > We have a DataLayer which uses NHibernate to Persist the objects in > the Database. Now my question -- whether we can achieve the above > using NHibernate's caching techniques. > -- You received this message because you are subscribed to the Google Groups "nhusers" group. To view this discussion on the web visit https://groups.google.com/d/msg/nhusers/-/abmJ00WjM0oJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
