#36690: Use case for EXTRA()
--------------------------------+--------------------------------------
Reporter: Gareth Leake | Owner: (none)
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: 5.2
Severity: Normal | Resolution: invalid
Keywords: QuerySet.extra | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+--------------------------------------
Changes (by Simon Charette):
* resolution: => invalid
* status: new => closed
Comment:
As ontowee pointed out this isn't a valid use case for `extra`; simply use
`Func` or `RawSQL` for this purpose or
[https://docs.djangoproject.com/en/5.2/howto/custom-lookups/ define your
own custom lookup].
--
Ticket URL: <https://code.djangoproject.com/ticket/36690#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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019a28eb7ce1-aba67db2-ae82-49d2-85ce-f3a183d285cb-000000%40eu-central-1.amazonses.com.
