#12712: syncdb doesn't create tables for m2m through-less fields that are added
on
the model after the class_prepared signal
---------------------------------------------------+------------------------
Reporter: IonelMaries | Owner: nobody
Status: new | Milestone: 1.2
Component: Database layer (models, ORM) | Version: 1.2-alpha
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by russellm):
Replying to [comment:7 IonelMaries]:
> Another case that still breaks:
>
> Running syncdb with these patches (any of them) after syncdb-ing an
empty database with an unpatched django doesn't create the m2m tables.
This is to be expected. Even though m2m fields are stored in a separate
table, they're not handled any differently to normal fields. If you add a
field to an existing table, Django doesn't update the table. Simliarly, if
you add an m2m field (or appear to add an m2m field, which is what is
happening here), Django doesn't create the m2m table.
--
Ticket URL: <http://code.djangoproject.com/ticket/12712#comment:8>
Django <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 django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
