#35453: ManyToMany field is a concrete field on the defining side.
-------------------------------------+-------------------------------------
Reporter: Harro | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 5.0
(models, ORM) |
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
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):
* cc: Mariusz Felisiak, Simon Charette (added)
* resolution: => invalid
* status: new => closed
Comment:
I think the docs could potentially be clearer but I don't think
`ManyToManyField` should have concrete as False.
I believe `local_concrete_fields` is when the column exists on the model's
table (rather than on a different table) and so is "local".
I think the docs are correct that `ManyToManyField` does have a database
column just not locally. Examples of non-concrete fields include
`GenericForeignKey`, `GenericRelation` and `ForeignObject`.
--
Ticket URL: <https://code.djangoproject.com/ticket/35453#comment:1>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018f7b59378d-c26b78f1-c460-4bfc-b3ad-7c24742c1b26-000000%40eu-central-1.amazonses.com.
