#2229: django-admin's syncdb does not check for missing many-to-many tables
----------------------------------+-----------------------------------------
Reporter: TwistedCommons.com | Owner: adrian
Status: closed | Component: django-admin.py
Version: SVN | Resolution: wontfix
Keywords: syncdb | Stage: Ready for checkin
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
----------------------------------+-----------------------------------------
Changes (by russellm):
* status: new => closed
* resolution: => wontfix
Comment:
I'm inclined to reject this idea. Syncdb doesn't have any schema-evolution
behaviour for data fields. Adding evolution-like behaviour for m2m fields
could lead to problems where a user modifies a model, resync's, and gets
*some* of their changes reflected in the database. My crystal ball forsees
nightmare threads on django-users debugging these problems.
I feel the right solution here is to get schema-evolution working, and in
the meantime, continuing the story of 'if you change your model, drop the
database and resync'.
--
Ticket URL: <http://code.djangoproject.com/ticket/2229#comment:4>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
