#35778: Use native JSONObject on Postgres 16+ with server side bindings
-------------------------------------+-------------------------------------
Reporter: john-parton | Owner: john-
| parton
Type: New feature | Status: assigned
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by john-parton):
Darn. That's a pretty massive con, I would agree. Let's say that's a non-
option then. Thank you for your insight.
So with respect to my open PR, it sounds like we should use the double-
colon as well, in the (probably unlikely case) that the field in question
has an index on it. Based on what you said, if we use
"CAST(%(expression)s)" it might result in an index a user defined with the
expectation it be used, going unused due to the text not being exactly the
same in the query. Make sense?
--
Ticket URL: <https://code.djangoproject.com/ticket/35778#comment:12>
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/010701924e76fd8c-b11ae40f-7f6c-40ae-b154-13c79edda793-000000%40eu-central-1.amazonses.com.
