Changes between Version 3 and Version 4 of SchemaEvolutionDesign

Timestamp:

Mar 9, 2012, 3:49:49 PM (13 years ago)

Author:

Joe Tennies

Comment:

--

SchemaEvolutionDesign

@@ -31 +31 @@
 * Store revision number of tables
 * Store updates as python scripts
-* Reverse migrations? (from version 6 to version 4)
 * Modify database schemas (Will require updates to database API)
   * Add columns
@@ -51 +50 @@
   * Detect that data may be lost
 
-== Non-Goals ==
+=== Non-Goals ===
 
 * Autodetection of changes
   * This should be left for external tools like South or nashvegas to do
+* Reverse migrations? (from version 6 to version 4)
+
+= Code Design =
+
+== Signals ==
+
+=== pre_migration ===
+
+Parameters: 
+''app'' - the app to be migrated as a string
+''return_value''' - class that has a function to cancel the migration???
+
+Sent just before starting running migrations for an app.
+
+=== post migration ===
+
+Parameters: 
+''app'' - the app to be migrated as a string
+
+Sent just after migration successfully finishes for an app. Note that if the migrations fail in the middle of executing, this will not get called.