SaveOrUpdate has nothing to do with DB, it tells NHibernate to register the entity as a persistent entity and it puts it in the 1st level cache. You should never expect as a rule to hit the DB while saving/updating or deleting. You will get a hit or not depending on a lot of considerations...
Gustavo. On Mon, Oct 27, 2008 at 9:09 PM, Berke <[EMAIL PROTECTED]> wrote: > > And this makes sense to me, if I was using transactions right now, > I've not explicitly setup a transaction, so I would assume the > behavior would be to persist the update when I call SaveOrUpdate, > (sort of like an implicit transaction that my entire save should > commit or roll back). > > Josh > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
