• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint
Share this Page URL
Help

Chapter 22. Transaction Processing > Using Transaction Processing in a Client/S...

Using Transaction Processing in a Client/Server Environment

When dealing with transactions in a client/server environment, you must consider several additional issues: when and how transactions occur, what types of transactions are supported, and what types of problems can occur.

Implicit Transactions

When explicit transactions are not used, the way in which transactions are committed on the database server depends on what types of commands are being executed. In general, every line of code has an implicit transaction around it. This means that there is not a way to roll back an action because it is committed immediately on the database server. The exceptions to this rule are any SQL statements issued that modify data. These SQL statements (UPDATE, INSERT, and APPEND) are executed in batches; a transaction loop is implicitly placed around the entire statement. If any records involved in the SQL statement cannot be updated successfully, the entire UPDATE, INSERT, or APPEND is rolled back.


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint