#35413: FieldError: Unsupported lookup error message can be confusing.
-------------------------------------+-------------------------------------
Reporter: Alex | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | 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):
* stage: Unreviewed => Accepted
* summary:
FieldError: Unsupported lookup error message can be confusing on
DateTimeField
=> FieldError: Unsupported lookup error message can be confusing.
* type: Bug => Cleanup/optimization
Comment:
Replicated, this is also true of other fields.
I agree that saying something like `Unsupported lookup 'gt__foo'`,
`Unsupported lookup 'gt__'`, and `Unsupported lookup 'gt__lt'` would be
clearer.
--
Ticket URL: <https://code.djangoproject.com/ticket/35413#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018f29f0476c-2d314ddd-693b-494d-b426-e673824b6ade-000000%40eu-central-1.amazonses.com.
