Changes between Version 2 and Version 3 of BluePrintDatabaseMigration


Ignore:
Timestamp:
03/10/11 12:58:02 (10 years ago)
Author:
Pat Tressel
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrintDatabaseMigration

    v2 v3  
    88=== Motivation ===
    99
    10 Far too often, people make changes to the database schema or to the data with which the database is initially populated.  This causes pain and suffering for anyone with a live Eden instance who needs to upgrade their Eden software.  We should provide a way of easing the process of migrating a database to a new revision.
     10Far too often, people make changes to the database schema or to the data with which the database is initially populated.  This causes pain and suffering for anyone with a live Eden instance who needs to upgrade their Eden software.
     11
     12Web2py handles some simple schema changes, but the ones that cause problems are precisely the ones it can't handle, such as renaming a field or table, or adding a required non-null field, or requiring the creation of new records from current ones (e.g. if a single foreign key reference is removed from a table and is placed in a new relationship table), or where the data themselves are modified.
     13
     14We should provide a way of easing the process of migrating a database to a new revision.
    1115
    1216=== Proposed project ===