On 8/14/07, George Vilches <[EMAIL PROTECTED]> wrote: > > George Vilches wrote: > Unfortunately, since there's only a syncdb signal, I can't even do > things like a reset on it, and there's definitely no way currently to > get the SQL generated from my syncdb signal. Being able to get the > CREATE and DROP statements in text as well as each individually would be > a huge boon to this type of use (and any dynamic model use in general). > > Is that a more reasonable example?
That maybe explains the need for a signal on reset - except that I'd be an advocate for removing the reset command altogether. It's pretty badly broken as it currently stands - any tables with m2m relations will have some major difficulties using it (if you're using a database with row referential integrity, anyway). Getting access to the CREATE and DROP statements is a separate issue - and was the reason for my suggesting the SQL logger. The idea would be that you could call _any_ manage.py command with the --sql flag, and you would get the SQL output to the screen, rather than the database. 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 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?hl=en -~----------~----~----~----~------~----~------~--~---
