Okay, I figured it out. By calling Flush you can have it run the statements. Sigh, i've been staring at this too long.
On Aug 23, 9:51 am, MattO <[email protected]> wrote: > FYI, when I was saying "CommitChanges", I meant to say > transaction.Commit which is using an ITransaction. > > I use the ShowSQL parameter to see what happens at the database level, > but for Deletes nothing gets sent unless you commit the transaction, > so I can't truely test my delete operations. > > On Aug 23, 9:46 am, MattO <[email protected]> wrote: > > > > > I'd like to unit test my delete operations more thourougly in > > nHibernate but can't figure out how to do it. > > > Right now I issue the delete statement and rollback the transaction > > after that. This test succeeds just fine. If you examine the SQL you > > will notice no delete statements are sent to database :( > > > Now if I try to do CommitChanges the unit test fails because there was > > problems with my mapping file and how cascading deletes were setup. > > > How can I do CommitChanges without actually committing the transaction > > so I can see if the delete statements would actually work properly?- Hide > > quoted text - > > - Show quoted text - -- 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.
