--- "Jeffrey W. Baker" wrote:
Yup.
Machine A is controlling a transaction across Machine X and Machine Y. A
modifies a row in X and adds a row to Y. A commits X, which succeeds. A
commits Y, which fails.
Now what?
A cannot guarantee a recovery on machine X because there might already be
other transactions in flight on that record in that database. A cannot
just try to put the record back the way it used to be, because now the
commit might fail on X. The data is inconsistent.
--- end of quote ---
You can buy a solution to that. High-priced java application servers like iPlanet's
call this "two-phase commit" and hide it behind JTA (using IBM's Encina engine in this
case). For only $35k per CPU.
There must be a CPAN module for it. ;)
-Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
