#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):
Pros in favor or removing `::` in favor of `CAST`
* Less code
* Generated SQL on Postgres will match other RDMS output in many cases
* It's more explicit
* "Standardization"
Cons
* It's not _strictly_ required to solve this specific issue
* Users more familiar with Postgres likely would find the double-colon
notation more readable in most circumstances
* Perhaps there's a goal to make the generated SQL look as if it were
written by an experienced programmer writing in that specific dialect.
"Idiomatic" postgres?
--
Ticket URL: <https://code.djangoproject.com/ticket/35778#comment:10>
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/010701924e2b5e9a-659c1c86-c2eb-4be9-b387-3744ba478ef0-000000%40eu-central-1.amazonses.com.
