#35453: ManyToMany field incorrectly identified as a concrete field on the
defining
side.
-------------------------------------+-------------------------------------
Reporter: Harro | Owner: Ryan P
| Kilby
Type: Bug | Status: closed
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls <jacobtylerwalls@…>):
In [changeset:"9575f813afe8f6d40b016cf302d6871f5d38517e" 9575f813]:
{{{#!CommitTicketReference repository=""
revision="9575f813afe8f6d40b016cf302d6871f5d38517e"
[6.0.x] Fixed #35453 -- Made ManyToManyField.concrete False.
ManyToManyField was already excluded from fields, concrete_fields,
and local_concrete_fields in Options.
Backport of f9a44cc0fac653f8e0c2ab1cdfb12b2cc5c63fc2 from main
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35453#comment:15>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019974469034-4eaf8b45-4236-40d7-9661-35813fccfeb2-000000%40eu-central-1.amazonses.com.
