Changes between Version 18 and Version 19 of BluePrintDatabaseMigration


Ignore:
Timestamp:
04/07/11 18:10:47 (11 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrintDatabaseMigration

    v18 v19  
    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  * Provide a UI that allows whoever made the schema change to tell how to convert the database.
    111    For instance, this could include allowing them to:
    112   * Match up renamed tables and columns.
    113   * Describe how to set a value for new unique columns in existing records.
    114   * Provide a template for subdividing records when tables are refactored (in straightforward cases).
    115   * Provide a script to do more complex conversions.
    116   * This subproject would only record the requested conversions, not apply them.
     110 * Possible (contention: see 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.
    117118 * Design a process to convert a database at one revision into the form needed by a later revision.
    118119  * Write a script that converts from revision N to N+1 given the conversion info from the above