From 872bb1acd51ecb4e4cf9ffb254ca5a7c471ed408 Mon Sep 17 00:00:00 2001 From: bascht Date: Mon, 30 Jun 2008 14:51:03 +0000 Subject: [PATCH] - added doc for a little workaround when migrating models with changed attributes --- manual/docs/en/migration.txt | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/manual/docs/en/migration.txt b/manual/docs/en/migration.txt index 540e502ce..8036f337b 100644 --- a/manual/docs/en/migration.txt +++ b/manual/docs/en/migration.txt @@ -158,4 +158,21 @@ CREATE TABLE migration_version ( version INT ); INSERT INTO migration_versiont (version) VALUES (1); -If you prefer the one operation per migration, you may be starting at step 9 or 30 or who knows. If you have no existing tables or data that you care to keep, you can drop all your existing tables and call the migration function to create all your initial tables. \ No newline at end of file +If you prefer the one operation per migration, you may be starting at step 9 or 30 or who knows. If you have no existing tables or data that you care to keep, you can drop all your existing tables and call the migration function to create all your initial tables. + +If you had to migrate a few steps down, you might get stuck between two migration steps if your model is out of sync with your table. +Assume that migration step 3 adds a new attribute to your model - and step 2 tries to access that model, you cannot migrate to step 3, because the table doesn't know about the new attribute: + +$migration = new Doctrine_Migration('/path/to/migration_classes'); + +// Current version is 3 +echo $migration->getCurrentVersion(); // 3 + +$migration->migrate(0); // takes you from 3 to 0 +$migration->migrate(3); // should take you from 0 to 3 but might throw an error if your model is out of sync + +echo $migration->getCurrentVersion(); // 1 + + +A simple workaround is to comment out the new attribute in your model file, migrate up stepwise and uncomment the attribute, when you're done. + \ No newline at end of file