Changes between Version 5 and Version 6 of SchemaEvolutionProposal

Timestamp:

Apr 24, 2006, 2:00:57 PM (19 years ago)

Author:

brantley

Comment:

--

SchemaEvolutionProposal

@@ -160 +160 @@
   * 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.
   * 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.
-  * 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"?
+  * 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.
 
 === Comments ===