#32321: Add system checks for invalid model field names for functional indexes
in
Meta.indexes.
-------------------------------------+-------------------------------------
Reporter: Mariusz Felisiak | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: 3.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Someday/Maybe
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* stage: Accepted => Someday/Maybe
Old description:
> The current system checks don't cover invalid models fields in functional
> indexes. This is not straightforward because resolving expressions with
> non-existent throws `FieldError`, so we cannot just collect columns from
> `Query._gen_cols()`.
>
> I attached tests.
New description:
The current system checks don't cover invalid models fields in functional
indexes. This is not straightforward because resolving expressions with
non-existent throws `FieldError`, so we cannot just collect columns from
`Query._gen_cols()`.
Follow up to #26167.
I attached tests.
--
Comment:
Sorry Hasan, I should mark this ticket as "someday", it's a follow up to
#26167. It will be valid after merging
[https://github.com/django/django/pull/11929 PR].
--
Ticket URL: <https://code.djangoproject.com/ticket/32321#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 on the web visit
https://groups.google.com/d/msgid/django-updates/065.756e64e6cef4b423711dc9ae158e2977%40djangoproject.com.
