Does Versioned Schema Management Guarantee Atomic Rollback Post-Change?
SourceEngine Schema Evolution The versioned schema management system tracks applied schema revisions for controlled evolution. The uncertainty lies in the atomicity guarantee when a schema change is followed by a rollback. What is the documented behavior for transactional boundaries during schema rollback? Does the system ensure data integrity across schema
sourceengine