 |
BorlandTalk.com Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Hifni Guest
|
Posted: Fri Feb 02, 2007 9:11 am Post subject: Transaction Handling in Multitier |
|
|
Hi,
I would like to know whether it is a good thing controling transaction in the application server and not in the client side?
For example, something in the following form of code in the application server:
Try
Database.StartTransaction;
//Do the Neccessary Insert,Update or Delete Transaction
UpdateQuery.ExecSQL(ukUpdate);
Database.Commit;
Except
Database.Rollback
End;
Would like to get your comments on this.
Thank You,
Hifni |
|
| Back to top |
|
 |
Clay Shannon Guest
|
Posted: Fri Feb 02, 2007 7:08 pm Post subject: Re: Transaction Handling in Multitier |
|
|
"Hifni" <hifni (AT) delphix (DOT) net> wrote in message
news:45c2c174$1 (AT) newsgroups (DOT) borland.com...
| Quote: |
Hi,
I would like to know whether it is a good thing controling transaction in
the application server and not in the client side?
For example, something in the following form of code in the application
server:
Try
Database.StartTransaction;
//Do the Neccessary Insert,Update or Delete Transaction
UpdateQuery.ExecSQL(ukUpdate);
Database.Commit;
Except
Database.Rollback
End;
|
That's the way I do it in the server app of my MIDAS/Datasnap suite. I would
like to do something similar on the client, but I don't see a way to do that
"Execute and Commit or Rollback" type of thing using the TClientDataSets
(which are hooked, of course, to TDatasetProviders on the server which are,
in turn, hooked to TADOStoredProcedures).
--
Check out my books here: http://www.lulu.com/blackbirdcraven
and/or read about "Zany Warble" here: http://funniestnovelever.blogspot.com/ |
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|