Russell Keith-Magee wrote: > Glad you like it. I'm hoping to get some time in the next week or so > to finish off the few things that are needed before I bug Adrian for > permission to commit. In the meantime, if you have any suggestions or > comments, let me know.
Maybe I could just throw in another use case and we can see if the dump/restore facility will work in this way too... Right now I'm working on a project that we're developing a new data model with. The content team is already starting to input data. Occasionally I find a need to add a new database column to support something new. This is your typical schema evolution need. If I could dump the current data, run an sqlreset, and reload the data, that would be amazingly helpful. (At least until schema evolution comes online or even as an alternative approach after it's available.) Would/Could it work like this? Is the dump/restore facility tied to fixtures? I see a dumpdb option in your patch but not a reloaddb (or the like)... just a 'installfixture'. -Rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
