#19580: Unify reverse foreign key and m2m unsaved model querying
-------------------------------------+-------------------------------------
Reporter: Anssi Kääriäinen | Owner: Pavel
Type: | Druzhinin
Cleanup/optimization | Status: assigned
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Pavel Druzhinin):
Rebased the previous PR https://github.com/django/django/pull/11807.
I would like to get some clarification on this old ticket, took it under
easy-pickings tag.
https://github.com/django/django/pull/11807#pullrequestreview-344544165 -
this is the last comment from where I started to search next steps to
complete the ticket.
It leads to the undone comments:
1. https://github.com/django/django/pull/8570#pullrequestreview-113177526
Should I move all tests from m2m_through_regress to many_to_many or some
particular tests?
2. https://github.com/django/django/pull/8570#pullrequestreview-113506649
I see prepared changelogs in comment
https://github.com/django/django/pull/11807#issuecomment-612404721, but
don't know where to place them in codebase. Could you explain?
Thanks!
--
Ticket URL: <https://code.djangoproject.com/ticket/19580#comment:35>
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/066.15e193518a566e13299f1f1552d8b1ce%40djangoproject.com.
