On 10/19/07, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote: > > > On 18-Oct-07, at 11:28 AM, Derek Anderson wrote: > > > what are thoughts on a new option to sqlreset (and others, as > > appropriate) to apply the change to the db? something like this: > > > > ./manage.py sqlreset --apply > > i thought sqlreset was deprecated
"Not actively promoted" might be a better description. It certainly _could_ be deprecated in the future. I wouldn't raise expectations that it will be kept long term. (sql)reset is broken as currently implemented, and as far as I can make out, it can't really be fixed without some major changes. However, I'm not convinced it is worth spending the effort to fix the problems that exist. The problem (sql)reset is intended to solve would be better served by a good schema evolution framework. In the absence of an officially adopted schema-evolution approach, there is still a place for (sql)reset, even in a limited/partially broken state. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
