| From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | andrew(at)dunslane(dot)net, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Shouldn't jsonpath .string() Unwrap? |
| Date: | 2024-06-12 20:10:01 |
| Message-ID: | 5E092D41-99CD-4BE6-9B3D-5E8EEA38C032@justatheory.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Jun 12, 2024, at 4:02 PM, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> Adding Andrew.
Thank you.
> I'm willing to call this an open item against this feature as I don't see any documentation explaining that string() behaves differently than the others.
Maybe there’s some wording in the standard on this topic?
I’m happy to provide a patch to auto-unwrap .string() in lax mode. Seems pretty straightforward.
D
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2024-06-12 20:11:35 | Re: Proposal for Updating CRC32C with AVX-512 Algorithm. |
| Previous Message | David G. Johnston | 2024-06-12 20:02:44 | Re: Shouldn't jsonpath .string() Unwrap? |