Export to GitHub

ruckusing - issue #2
Update schema_info verison number after each step in migration
Posted on Oct 9, 2007 by
Happy Rabbit
What steps will reproduce the problem? 1. Update schema_info verison number after each step in migration
What is the expected output? What do you see instead? In a 10 step migration if #5 fails the schema_info version column will reflect that you are at version 1 when in reality version 4 has been executed with success.
Comment #1
Posted on Oct 24, 2007 by Swift GiraffeFixed.
The migration logic has been redone so that the schema version is updated after each successful migration execution.
Status: Fixed
Labels:
Type-Defect
Priority-Medium