| From: | Peter van Hardenberg <pvh(at)pvh(dot)ca> |
|---|---|
| To: | Marko Tiikkaja <marko(at)joh(dot)to> |
| 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 20:15:31 |
| Message-ID: | CABTbUpik8-x8Oq-GOk3NffY0pcRG3LfpKC9Hr1KYNDYfWzLv5g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Great question, Marko. If you can point me towards an example I'll take a
look, but I'll proceed with the current understanding and suggestions and
see what people have to say.
On Mon, May 23, 2016 at 10:47 AM, Marko Tiikkaja <marko(at)joh(dot)to> wrote:
> On 2016-05-23 18:55, Peter van Hardenberg wrote:
>
>> 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?
>>
>
> What about cases like json_whatever($1) which previously worked but will
> now be ambiguous? (Or will they somehow not be ambiguous?)
>
>
> .m
>
--
Peter van Hardenberg
San Francisco, California
"Everything was beautiful, and nothing hurt."—Kurt Vonnegut
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2016-05-23 20:17:15 | Re: Changed SRF in targetlist handling |
| Previous Message | Tom Lane | 2016-05-23 20:15:13 | Re: Changed SRF in targetlist handling |