Lucid Outsourcing Solutions

  Introduction The code reads two database tables. It updates an inventory record. It inserts an order line. It updates the customer’s loyalty balance. Halfway through, the loyalty update fails — the column does not exist on the customer table after a schema change nobody documented. ColdFusion throws an error. You expect the transaction to roll back. You expect the inventory and order records to revert. You expect the database to look exactly as it did before the operation started. You expect atomicity. What you get is an inventory record that decremented, an order line that exists with a phantom customer reference, and an error log entry that says nothing about why the rollback failed. Read More