From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Peter van Hardenberg <pvh(at)pvh(dot)ca> |
Cc: | "pgsql-hackers(at)postgresql(dot)org Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Calling json_* functions with JSONB data |
Date: | 2016-05-23 17:14:55 |
Message-ID: | CAKFQuwZGOzxbc2pQh1WaaD9HQuDs0hHVUQwtiXoT=YmZWWZcRA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, May 23, 2016 at 12:55 PM, Peter van Hardenberg <pvh(at)pvh(dot)ca> wrote:
> Hi there,
>
> I noticed it was very easy to accidentally call the json_* form of JSON
> manipulation functions with jsonb data as input. This is pretty
> sub-optimal, since it involves rendering the jsonb then reparsing it and
> calling the json_* form of the function.
>
> Fortunately, this seems quite easy to resolve by taking advantage of our
> ability to add json_*(jsonb) form of the functions.
>
> I talked this over with Andrew who had no objections and suggested I float
> it on the list before writing a patch. Looks pretty straightforward, just a
> few new data rows in pg_proc.h.
>
> Anyone have any concerns or suggestions?
>
>
Please provide an example of what you are talking about.
SELECT json_array_length('[1,2]'::jsonb)
ERROR: function json_array_length(jsonb) does not exist
-- The function name is "jsonb_array_length"; and there is no implicit cast
between the two.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-05-23 17:22:09 | Re: Parallel safety tagging of extension functions |
Previous Message | Tom Lane | 2016-05-23 17:10:29 | Re: Changed SRF in targetlist handling |