Changes between Version 20 and Version 21 of BluePrintDatabaseMigration

Timestamp:

04/12/11 02:18:33 (15 years ago)

Author:

Pat Tressel

Comment:

--

BluePrintDatabaseMigration

@@ -108 +108 @@
   * Set this up to produce reports revision-by-revision (e.g. have the continuous integration build,
     which is triggered by commits to the Eden trunk, run a script).
- * Possible (contention: see [BluePrintDatabaseMigration#Franscomments Fran's comments] above)
-  * Provide a UI that allows whoever made the schema change to tell how to convert the database.
-    For instance, this could include allowing them to:
-   * Match up renamed tables and columns.
-   * Describe how to set a value for new unique columns in existing records.
-   * Provide a template for subdividing records when tables are refactored (in straightforward cases).
-   * Provide a script to do more complex conversions.
-   * This subproject would only record the requested conversions, not apply them.
+ * (Possible contention: see [BluePrintDatabaseMigration#Franscomments Fran's comments] above.)
+   Provide a UI that allows whoever made the schema change to tell how to convert the database.
+   For instance, this could include allowing them to:
+  * Match up renamed tables and columns.
+  * Describe how to set a value for new unique columns in existing records.
+  * Provide a template for subdividing records when tables are refactored (in straightforward cases).
+  * Provide a script to do more complex conversions.
+  * This subproject would only record the requested conversions, not apply them.
  * Design a process to convert a database at one revision into the form needed by a later revision.
   * Write a script that converts from revision N to N+1 given the conversion info from the above