We're using the ado.net provider for SQL Anywhere 10.0.1 and call
stored procedures. Although our stored procedure already encapsulates
an insert in a transaction, the c# routine that calls the procedures
encapsulate the stored procedure calls again using a .net
SATransaction object. Our problem is that calling the Rollback()
method does not rollback the transaction, i.e. the inserted record is
still in the DB. This is unwanted for our integration tests, since we
want to rollback all changes after our tests succeed so that we can
have reproduceable tests. Is there any known problem with
SATransaction we should be aware of?

srsanchez75 (AT) googlemail (DOT) com wrote:
I'm not sure I understand your question. Are you saying that you have a
stored procedure that has a commit in it ("already encapsulates an
insert in a transaction"), but after you call the stored procedure you
want to be able to execute a rollback and undo the operation that was
committed in the stored procedure?

--
Reg Domaratzki, Sybase iAnywhere Solutions
Please reply only to the newsgroup

Documentation : Exercise your WRITE @DocCommentXchange: DCX.sybase.com
SQL Anywhere Patches and EBFs : http://downloads.sybase.com/swd/base.do
-> Choose SQL Anywhere
-> Optionally set filter to "Display ALL platforms IN ALL MONTHS"