#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 Simon Charette):
I'm of opinion that we should try to generate the same SQL with and
without server-side bindings enabled. That should put us in a better place
for eventual support for prepared statements (#20516).
As for the parenthesis wrapping I think that another option that wasn't
discussed is to use a `Func(expression, template="CAST(%(expressions)s AS
text)")` instead of `Cast` in this particular case to avoid the parsing
ambiguity in `as_postgres` while leaving `Cast.as_postgres` alone.
--
Ticket URL: <https://code.djangoproject.com/ticket/35778#comment:7>
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/010701924d2f9b7c-b54fccc0-23d6-440d-901e-fa5f399271a2-000000%40eu-central-1.amazonses.com.
