#29482: simplify KeyTransform to always use the 'nested_operator'
-------------------------------------+-------------------------------------
Reporter: David De Sousa | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: contrib.postgres | Version: 2.0
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => wontfix
* stage: Accepted => Unreviewed
Comment:
Replying to [comment:7 David De Sousa]:
> Although if support is added to the `Index` class, this discussion is
irrelevant since the index can be created with the same logic the
`KeyTransform` classes use, using the -> and ->> operators when dealing
with root-level keys and the #> and #>> operators when traversing, this is
what I'm doing in a management command that handles the index creation for
my use case after I found out about this behavior.
`Index()` supports creating functional and partial indexes based on
`JSONField` key transforms (see
[https://github.com/django/django/blob/f97401d1b184406d2e24f11eddbdaca8bbc360e3/tests/schema/tests.py#L3108-L3155
tests]), so as far as I'm aware this can be closed.
Closing as "wontfix", because we will not change the current operators.
--
Ticket URL: <https://code.djangoproject.com/ticket/29482#comment:9>
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/063.6b7924de4535ce6c613683cbd56f562b%40djangoproject.com.
