Code

Changes between Version 5 and Version 6 of SchemaEvolutionProposal


Ignore:
Timestamp:
04/24/06 12:00:57 (8 years ago)
Author:
brantley
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SchemaEvolutionProposal

    v5 v6  
    160160  * To add funcitonality for rolling back the changes, one would have to add "pre_rollback" and "post_rollback" keywords to the {{{evolve()}}} function.  And we'd have to keep a record of all past models much like the shadow model.  You could easily then, assume that on rollback: create -> drop, drop -> create, and rename is reversed. 
    161161  * If one could keep the shadow models in the database, that would be best, but I'm not sure the best way of doing that. 
    162   * Are there any other operations other than "create", "drop", and "rename", that might need to be expressed and aren't obvious (such as changing a field options like "maxlength"? 
     162  * Are there any other operations other than "create", "drop", and "rename", that might need to be expressed?  Obvious things, such as changing a field options like "maxlength", which aren't ambiguous, don't need directives. 
    163163 
    164164=== Comments ===