#23498: V1.7 migration doesn't properly rebuild the through table from 3rd party
library
-------------------------------+--------------------------------------
Reporter: variable | Owner: nobody
Type: Uncategorized | Status: closed
Component: Migrations | Version: 1.7
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by timgraham):
I am not sure how it would work, but for Django to try to introspect
indexes and remove any it doesn't expect seems dangerous. The field looks
like somewhat of a hack. If possible, I would recommend using a
`ForeignKey` instead.
--
Ticket URL: <https://code.djangoproject.com/ticket/23498#comment:3>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.608255c938fe586e268e295f6c85e071%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
