WebSpeed
Developer’s Guide
All-or-nothing Processing
Suppose a customer calls to change an order for four sweat bands to nine sweat bands. This means you must make two changes to your database:
What if you changed the quantity field in the order-line record and are in the midst of changing the allocated field in the item record, when the machine goes down? You want to restore the records to their original state. That is, you want to be sure that WebSpeed changes both records or changes neither.
Figure 9–3 shows this scenario for a database similar to Sports2000 (same tables, different data).
Figure 9–3: Database Transaction Involving Two Tables
![]()
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |