What would be a practical example when one would user Persist, rather then Save? Will Persist override cascade settings on the relationships? I mean Save worked fine so far, but there must be a good reason why Persist was added.
On Nov 20, 9:20 am, Fabio Maulo <[email protected]> wrote: > To be short... > Persist will persist the whole graph using cascade. Make persistent an > object mean know its POID. > Save mean Save an instance and enlist cascade actions. > > 2009/11/20 epitka <[email protected]> > > > > > > > Can somebody point me to some blog or document that discusses > > Session.Persist and the semantics of it. What is the difference > > between Session.Save and Session.Persist. > > > -- > > > 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]<nhusers%[email protected] > > > > > . > > For more options, visit this group at > >http://groups.google.com/group/nhusers?hl=. > > -- > 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=.
