On 8/15/07, Deryck Hodge <[EMAIL PROTECTED]> wrote: > Why not, rather than adding another option in django.core.management, > have the contenttypes app do this? The existing post_syncdb hook > could be extended to clear unused content types as well as create new > ones. > > You would have to remember to run syncdb after a reset though, but > this would be better than reseting all content types or adding another > option IMHO.
After reading the code in django.contrib.contenttypes.management it does seem the natural place. And it makes sense to me that content types would tidy up after itself if it noticed orphaned content types. Is this a common problem for people or just me? I don't run into it with every app, but I do refactor my models often times and run into this, and think it would be nice if there were a more automated way to clean up those tables. -Rob --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
