#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: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Pavel Druzhinin):
Replying to [comment:37 Mariusz Felisiak]:
> Thanks for this patch, however it's not ready for review. Please fix
tests and `isort`.
Hello, it seems I need help to fix this error. I'm not sure code from
previous contributor is correct and I don't fully understand the subject
of this bug (m2m relations).
What is better to do: remove label `easy pickings` and try another bug or
someone could help me with fixing this bug?
P.S. Please, don't think for nagging. I really don't want to drop the
ticket silently and want to continue to contribute at the same time.
Thanks in advance with your advice how best to proceed.
--
Ticket URL: <https://code.djangoproject.com/ticket/19580#comment:38>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/066.ed3fd074c068e289d3f71f0a29c6d722%40djangoproject.com.
