| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Jan Bernitt <jaanbernitt(at)gmail(dot)com> |
| Cc: | Steve Midgley <science(at)misuse(dot)org>, "pgsql-sql(at)lists(dot)postgresql(dot)org" <pgsql-sql(at)lists(dot)postgresql(dot)org> |
| Subject: | object mapping for json/jsonb columns |
| Date: | 2024-08-27 16:17:29 |
| Message-ID: | CAKFQuwbtZC7cUKMmGy51PYCvAQM4jSK2s1TZwb888H=4ayFHXQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Tuesday, August 27, 2024, Jan Bernitt <jaanbernitt(at)gmail(dot)com> wrote:
>
> So if nothing like this exists in postgreSQL I highly suggest starting to
> design JSON(B) functions that offer this flexibility :)
>
PostgreSQL is both extensible and open source. I highly suggest this seems
like a perfect place for some enterprising people to leverage those aspects
to improve things instead of burdening the core developers with more work.
Given that pluggable procedural languages already have this kind of tooling
I’d even hazard to say this is a solved issue for those that go against
normalization of a relational model.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Joseph Krogh | 2024-08-27 16:27:26 | Re: ORDER BY elements in ARRAY |
| Previous Message | Jan Bernitt | 2024-08-27 16:05:00 | Re: object mapping for json/jsonb columns |