[nhusers] Transaction Rollback Behavior

[Josh Berke]

How should nHibernate behave when a roll back is issued for example take the following use sequence: User creates a new session and starts a transaction. User updates his entity, and calls SaveOrUpdate. User tries to commit the transaction; however, an error occurs. User calls Rollback on the transaction. User tries to save a different entity, User calls flush At step six, what I am noticing is that nHibernate is trying to process the entity from step 2 resulting in the same error in step 3. Since this occurred within a transactional scope shouldn't nHibernate throw out the dirty entity when a rollback occurs? Thanks, Josh --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to nhusers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---