How does TransactionScope roll back transactions?

Question

I'm writing an integration test where I will be inserting a number of objects into a database and then checking to make sure whether my method retrieves those objects.

My connection to the database is through NHibernate...and my usual method of creating such a test would be to do the following:

NHibernateSession.BeginTransaction();  //use nhibernate to insert objects into database //retrieve objects via my method //verify actual objects returned are the same as those inserted  NHibernateSession.RollbackTransaction(); 

However, I've recently found out about TransactionScope which apparently can be used for this very purpose...

Some example code I've found is as follows:

public static int AddDepartmentWithEmployees(Department dept) {      int res = 0;      DepartmentAdapter deptAdapter = new DepartmentAdapter();     EmployeeAdapter empAdapter = new EmployeeAdapter();     using (TransactionScope txScope = new TransactionScope())     {          res += deptAdapter.Insert(dept.DepartmentName);         //Custom method made to return Department ID          //after inserting the department "Identity Column"         dept.DepartmentID = deptAdapter.GetInsertReturnValue();         foreach(Employee emp in dept.Employees)         {              emp.EmployeeDeptID = dept.DepartmentID;             res += empAdapter.Insert(emp.EmployeeName, emp.EmployeeDeptID);          }         txScope.Complete();      }     return res;  } 

I believe that if I don't include the line txScope.Complete() that the data inserted will be rolled back. But unfortunately I don't understand how that is possible... how does the txScope object keep a track of the deptAdapter and empAdapter objects and their transactions on the database.

I feel like I'm missing a bit of information here...am I really able to replace my BeginTransaction() and RollbackTransaction() calls by surrounding my code using TransactionScope?

If not, how then does TransactionScope work to roll back transactions?

Answer 1

Essentially TransactionScope doesn't track your Adapter's, what it does is it tracks database connections. When you open a DB connection the connections will looks if there is an ambient transaction (Transaction Scope) and if so enlist with it. Caution if there are more the one connection to the same SQL server this will escalate to a Distribtued Transaction.

What happens since you're using a using block you are ensuring dispose will be called even if an exception occurs. So if dispose is called before txScope.Complete() the TransactionScope will tell the connections to rollback their transactions (or the DTC).