#36480: FieldError when referencing a nonexistent alias provides less
information
than nonexistent annotation
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: (none)
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: typo | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):
* easy: 1 => 0
* stage: Unreviewed => Accepted
Comment:
Thank you! Agree any aliases should be listed if they are a valid option
(so `order_by()`, `filter()` etc). But not on the occasions that it's not
valid, e.g. for `aggregate()`
I've tested the solution and it also lists for `aggregate()` which
wouldn't be a valid choice so will unset "easy" as I think it needs a bit
more looking into
--
Ticket URL: <https://code.djangoproject.com/ticket/36480#comment:1>
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/01070197ab6e662a-3bf9db59-31f6-4699-9c04-964a90f6aaf1-000000%40eu-central-1.amazonses.com.
