#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 -------------------------------------+------------------------------------- Comment (by Harro):
Which column does a ManyToMany have then? As far as I see it it has a table with has two (or more) columns pointing to two different tables, so why doesn't the other side of the ManyToMany not also have a column? `local_concrete_fields` is `local_fields` filtered on the concrete flag, but I can't find where the local_fields is filled in the source code, but it does not contain the ManyToMany fields defined on the model (so far that's correct) Also, the documentation doesn't mention the `local_fields` nor the `local_concrete_fields` so techically they shouldn't be used, but the get_field(s) api calls are documented, so I expect it to give me the information I need, as to which models are actually on a database table without extra weird conditions to exclude specifically one side of the ManyToMany relation. -- Ticket URL: <https://code.djangoproject.com/ticket/35453#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 django-updates+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/0107018f7b761d1b-22f4816a-70b9-4e85-96bf-cf660990ba74-000000%40eu-central-1.amazonses.com.