http://qs321.pair.com?node_id=417657


in reply to Re^2: Automated testing of database classes
in thread Automated testing of database classes

I can imagine that Sybase and MS SQL Server have identical transaction semantics.

This only works if you can do it consistently, but here is how to nest transactions and limit the rollback scope so that it matches that of e.g. a procedure:

begin tran save tran the_procedure_name --modify stuff if ... error ... begin rollback tran the_procedure_name commit tran return 1 end --success commit tran return 0

You start with beginning a transaction and immediately saving the transaction to a named savepoint. I've asked around and this doesn't seem to incur very much overhead.

If everything works okay, just commit once to end the outermost transaction.

If anything goes wrong, first rollback to the named savepoint, then commit the transaction (to make sure it's nested properly).

/J