Code

Changes between Version 8 and Version 9 of SchemaEvolutionProposal


Ignore:
Timestamp:
04/24/06 13:28:14 (8 years ago)
Author:
brantley
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SchemaEvolutionProposal

    v8 v9  
    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. 
    162162  * 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. 
    163   * pbx brings up that we might want to evolve from, say version 3 to version 4, even if version 5 is available.  I'm not sure how to perform this with this system, other than commenting the version 5 code.  Maybe there could be a __target_version__ directive at the top of the evolution file that could be altered. 
     163  * pbx brings up that we might want to evolve from, say version 3 to version 4, even if version 5 is available.  I'm not sure how to perform this with this system, other than commenting the version 5 code.  Maybe there could be a {{{__target_version__}}} variable at the top of the evolution file that could be altered.