#26327: Add JSONB_AGG to contrib.postgres
-------------------------------------+-------------------------------------
Reporter: Tomasz Nowak | Owner: Mads
| Jensen
Type: New feature | Status: new
Component: contrib.postgres | Version: master
Severity: Normal | Resolution:
Keywords: JSON postgres | Triage Stage: Accepted
aggregate |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
As mentioned above I think we should just rename the aggregate `JSONBAgg`
(or whatever case variant we choose) and be done with it. It's unfortunate
that we didn't name the `contrib.postgres` field `JSONBField` in the first
place and have a database agnostic one named
`django.db.models.fields.JSONField` now that other backends are shipping
with support for such a field but we should make the distinction clear
here.
We don't ship any field using the the PostgreSQL `json` datatype so it
doesn't make much sense to ship an expression for the `JSON_AGG` SQL
function IMHO. If we decide we still want to ship this tests should be
added for it at least. That will require defining a `JSONField` relying on
the `json` datatype.
--
Ticket URL: <https://code.djangoproject.com/ticket/26327#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.1f3655f69d175fee3057d4b7cc653a32%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.