FAQ: What is the transaction scope for the move edits to base operation?
What is the transaction scope for the move edits to base operation?
When an object class or feature class is registered as versioned with the move edits to base option and a save operation is performed, all edits for each modified class registered with the move edits to base option are compressed to their base tables in one database transaction. If an underlying DBMS error is encountered during the operation, the entire transaction is rolled back.
Understanding this behavior is important for application developers who are writing and creating database triggers on the classes base table because of the ramifications of the operation and the scope of the transaction.
For example, based on the definition of the trigger, if the trigger is executed during the move edits to base operation and the operation fails during a DML operation on the next class being modified, the entire transaction is rolled back, which rolls back any changes performed in the trigger.