Re: How to implement nested transaction

From: Arthur Hoornweg <antispam.hoornweg@xxxxxxxxxxxxx>
Date: Thu, 22 May 2008 11:17:20 +0200

Jack Zhong wrote:

Any instruction would be greatly appreciated.

Why not just one transaction? One transaction can easily
rollback changes made into multiple tables. No need to
nest them.

adoconnection1.begintrans;
try

// Your SQL here

//adoconnection1.execute().....
//adoconnection1.execute().....
//adoconnection1.execute().....

adoconnection1.committrans;
Except
adoconnection1.rollbacktrans;
Raise;
End;

--
Arthur Hoornweg

(In order to reply per e-mail, please just remove the ".net"
from my e-mail address. Leave the rest of the address intact
including the "antispam" part. I had to take this measure to
counteract unsollicited mail.)
.

References:
- How to implement nested transaction
  - From: Jack Zhong

Prev by Date: Re: Append and post - with standardvalues
Next by Date: ADOQuery Command Text does not return a result set
Previous by thread: Re: How to implement nested transaction
Next by thread: ADOQuery Command Text does not return a result set
Index(es):
- Date
- Thread

Relevant Pages

Re: Database design pattern question
... When it does it will be necessary to replace the disk drive and then rebuild your database using your most recent backup and a transaction file containing the transactions that have been processed since the backup was made. ... That is the problem that I really need to be able to have multiple copies of the databases being updated in parallel and to have the ability to synchronise them later. ... Maintain a transaction log and "replay" the transaction log for each copy of the database into the other databases.. ...
(comp.databases)
Re: computational model of transactions
... They just grouped multiple logical units of work together before issuing a commit. ... Serializing was handled by the normal concurrency features and isolation level. ... This is how one usually identifies what must go into a single transaction. ... Combining an integral number of logical units of work into a single transaction, however, does not introduce any risk of inconsistency. ...
(comp.databases.theory)
Re: computational model of transactions
... They just grouped multiple logical units of work together before issuing a commit. ... Serializing was handled by the normal concurrency features and isolation level. ... This is how one usually identifies what must go into a single transaction. ... Combining an integral number of logical units of work into a single transaction, however, does not introduce any risk of inconsistency. ...
(comp.databases.theory)
Re: Trouble with 2 tables connected by reference table
... each table that could have multiple values per store-date, ... were there actually 3 values for each store-date. ... I use two reference tables (dateRef, ... I then also want to bring in data from the transaction table, ...
(microsoft.public.access.queries)
Re: computational model of transactions
... conversations from years past about "multiple assignment". ... have to be only updates. ... problem that can not be dealt with simplyistic SQL based solutions. ... one still sees prior updates within the transaction. ...
(comp.databases.theory)