#24863: Make `django.db.models.Manager.from_queryset` copy over properties and
not
just methods
-------------------------------------+-------------------------------------
Reporter: Ram Rachum | Owner: Furkan
| Karataş
Type: New feature | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: assigned => closed
* resolution: => wontfix
* stage: Accepted => Unreviewed
Comment:
I agree with
[https://github.com/django/django/pull/16919/files#r1217066741 Lily], Mark
and Carl weren't convinced either. Using properties in `Queryset` to
perform queries is confusing, it gets even more puzzling when we realize
that some of them (e.g. `ordered`, `query`) have to be omitted in a
potential implementation. IMO, it's not worth the additional complexity.
--
Ticket URL: <https://code.djangoproject.com/ticket/24863#comment:13>
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/010701888fb63f8b-32842dcd-6ce8-4f4e-8e3c-73a1ce3b63d6-000000%40eu-central-1.amazonses.com.
