Saying it in another way then. Manually managing/reattaching detached objects is pretty difficult and very error-prone. If you forget to reattach an entity you can easily end up with multiple detached instances of the same entity, while no modifications were made to your entity between sessions opening/closing. How can I make detached object management easier?
On Aug 12, 10:02 pm, Fabio Maulo <[email protected]> wrote: > No it does not exists and it will never exists...What people call > "first-level-cache" in reality is the persistent-session-context that > represent the Unit-Of-Work; what you are asking is "break the > pattern Unit-Of-Work". > > 2009/8/12 Nelson <[email protected]> > > > > > > > Managing detached objects in a long running desktop application is > > kind of a pain, mostly because you can have several instances of the > > same entity (one per session instanciating it). Second level cache is > > great for not rehitting database, but it only store entity values, not > > entities objects, like first-level cache. > > > I'm brainstorming about the idea of a cross session first level cache. > > It would allow multiple sessions to return the same instance of data. > > It could use weak references so that unreferenced entities would be > > reloaded. > > > Does this kind of cache exists? If not, I guess it am not the first > > one to have this idea. Would that be a bad one? Or a very hard to > > implement one? > > -- > Fabio Maulo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. 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 -~----------~----~----~----~------~----~------~--~---
