On Mon, 2007-08-13 at 18:36 -0400, Todd O'Bryan wrote: > On Mon, 2007-08-13 at 16:31 -0500, Adrian Holovaty wrote: > > I'm proposing a "--with-fixture" flag to django-admin.py, so that you > > could do something like this: > > > > django-admin.py runserver --with-fixture=mydata.json > > > > With this command, Django would: > > > > * Delete the test database when the development server is stopped. > > > I'm in favor of everything but this part. I find myself wanting to go > poke around in the shell to check that everything has done what it's > supposed to. Also, given that you mention being able to serialize any > changes you've made as you quit, it sure would be nice if, until that > happens, you could still run dumpdata before the database disappears.
I agree. Either this or dumping the results to a new file before nuking the database. Poking around after the event is a pretty handy debugging technique for "wtf?!" moments. More than once I've gone into the runtests.py file and change SQLite's behaviour to keep the test database around for post mortem work. I suspect this would be more of a wish if I could also poke at the website (or when running Selenium tests). Otherwise, I'm +1 as well. Regards, Malcolm -- What if there were no hypothetical questions? http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
