Changes between Version 20 and Version 21 of BluePrintDatabaseMigration


Ignore:
Timestamp:
04/12/11 02:18:33 (10 years ago)
Author:
Pat Tressel
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrintDatabaseMigration

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