#24237: 1.7.4 requires derived ManyToManyFields to declare their internal_type
as
"ManyToManyField" or their add/remove migrations will do nothing
----------------------------+--------------------------------------
Reporter: ris | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Keywords: m2m migration add remove
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------------------------
According to the boffins on irc this is related to ticket #24104.
Using postgres and django 1.7.4, a custom ManyToManyField subclass that
doesn't override the get_internal_type method will generate empty sql when
a field add/removal migration is performed for it.
Whether or not this is desirable behaviour, it is *not* how 1.7.3 behaved
and will potentially trip up a good number of people.
--
Ticket URL: <https://code.djangoproject.com/ticket/24237>
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/046.e8329b510b982621e9ca900b333c282f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
