On Mon, 2006-02-27 at 19:26 -0800, Jacob Kaplan-Moss wrote: > Hey folks -- > > I've posted (over 1200 words of) my thoughts on schema evolution to the > wiki: http://code.djangoproject.com/wiki/SchemaEvolution. > > Any thoughts before I start on this?
Looks good. The only part that raised a few flags for me is the possibility of missing files (in the conclusion section). I can see the argument for allowing missing files (e.g. the evolution from version 3 to version 4 turned out to be bad, was never rolled out anywhere but to the testing systems, etc). But in production cases such as the use cases in this page, mistakes are going to be costly -- forgetting to roll out one upgrade and not getting a warning will cause stress down the road (oh, make the bad memories stop). Thinking about this some more, I guess if I was doing this in practice as an operations guy, I would routinely extract the list of evolution table entries for the package I think I just upgraded so that I could check it is the same on all machines. So maybe this isn't a big issue, but other people with large production system experience (the "Carol" use case) might want to think about what could go wrong here, too. But generally, this would be a great enhancement, I think. Nice writeup. Cheers, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
