Re: [Django] #35453: ManyToMany field incorrectly identified as a concrete field on the defining side. (was: ManyToMany field is a concrete field on the defining side.)

[Django]

#35453: ManyToMany field incorrectly identified as a concrete field on the defining
side.
-------------------------------------+-------------------------------------
Reporter: Harro | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Normal | Resolution:
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 Ryan P Kilby):

* cc: Ryan P Kilby (added)
* resolution: invalid =>
* status: closed => new
* summary: ManyToMany field is a concrete field on the defining side. =>
ManyToMany field incorrectly identified as a concrete field on the
defining side.

Comment:

I believe this ticket should be reopened. Related to
https://code.djangoproject.com/ticket/36481 and the discussion in
https://github.com/django/django/pull/19595, @charettes pointed out that
`ManyToManyField` is likely incorrectly identified as `concrete` and that
it should be investigated.
--
Ticket URL: <https://code.djangoproject.com/ticket/35453#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.