Changes between Version 8 and Version 9 of SchemaEvolutionProposal
- Timestamp:
- Apr 24, 2006, 3:28:14 PM (19 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SchemaEvolutionProposal
v8 v9 161 161 * 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 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. 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.