True, but I feel now like being dragged into a discussion I don't want to have. I simply want to have a way to say to my session: "Do you see this object graph? Can you please revert its state as it was when loaded from the database? It shouldn't be a big trick for you, because I know that you do know the loaded state."
Any comments on that guys? I've started writing my own revert-changes- cascading-action, but I'm stuck on how to revert the state of a collection. On Apr 30, 7:59 pm, Fabio Maulo <[email protected]> wrote: > On Fri, Apr 30, 2010 at 10:35 AM, tz > <[email protected]>wrote: > > > * Second level cache is for sharing data across transactions > > That is your interpretation of NH's cache. > > The cache is to limit DB hits. > When you change the state of an object you can say "bye bye" to your cache > (it depend, but as general concept we can simplify). > > -- > 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 > athttp://groups.google.com/group/nhusers?hl=en. -- 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.
