transactions

Hello,

I'm looking for any feedback or insight into the area of database replication for a cold-swap Drupal (5.x) site. This is my situation:

I'm not sure if the e-commerce module is affected by this change/update but we just received this email the other day about some major changes on how Authorize.net is handling transaction id's. Not sure if a patch needs to be created or not.

<

blockquote>Dear Authorize.Net Merchant:

In early October, Authorize.Net will be expanding the range of Transaction IDs issued by the payment gateway. Please read this e-mail thoroughly as it contains important information on how to ensure that your account is not affected.

I've released an in-development version of PressFlow Transaction for developers interested in convenient encapsulation of SQL transactions. The key features are intelligent use of scope for COMMITs and ROLLBACKs as well as safe, intelligent nesting of transactions to get exception-like semantics.

Usage details are on the project page. Requires PHP 5.

(I posted this to the High-Performance group because encapsulating updates in transactions can dramatically improve performance.)