Page Comparison

Optimistic locking workarounds

Could disable all through testing phase, and always set _version = 1.  Or at least could test this.  Did anyone (especially Stanford) try this?

Stanford created an Airflow DAG for dropping the OL triggers for inventory tables, monitors running migration jobs, and restores the OL triggers after 5 minutes have elapsed since the last active migration job. Will be testing starting todayJeff (Duke): Adding automatic updates and corrections for optimistic locking errors. Doing daily incremental updates. It tries to double-check the optimistic locking (looks up the version number) and updating the version number when he sends it in.  But sometimes updates twice (bound-withs!!!), and so errors.  Looks again for version number and sends again. Going for batch apis first.  When doing the error correction, does each record individually and looks up version number first.