#30035: many to many through table not recognisable in custom migration
-------------------------------------+-------------------------------------
Reporter: jainmickey | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 2.0
Severity: Normal | Resolution: needsinfo
Keywords: many to many, | Triage Stage:
through | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* status: new => closed
* resolution: => needsinfo
Comment:
It's unfortunately impossible to determine if Django is at fault with the
little details you provided so far.
The fact that you mention writing a custom migration without providing it
makes it likely that the issue lies there.
Please note that simply adding a `through` to a `ManyToManyField` or
manually adding an `AlterField` to add the through is not working yet
#23034.
If you have any details that proves that Django is at fault and that this
report is not a duplicate of #23034 please provide them and reopen this
issue.
--
Ticket URL: <https://code.djangoproject.com/ticket/30035#comment:2>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.82b6785a8d94363539accd09696510ed%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
