Re: SQL/JSON: functions - Mailing list pgsql-hackers

From Dmitry Dolgov
Subject Re: SQL/JSON: functions
Date
Msg-id CA+q6zcU=kiYPPcNK7EOuM08FDBNjco0U+=so1LwgfSKuCRsJ5Q@mail.gmail.com
Whole thread Raw
In response to Re: SQL/JSON: functions  (Nikita Glukhov <n.gluhov@postgrespro.ru>)
Responses Re: SQL/JSON: functions
List pgsql-hackers
> On Mon, Nov 26, 2018 at 5:11 PM Nikita Glukhov <n.gluhov@postgrespro.ru> wrote:
>
> On 26.11.2018 15:57, Dmitry Dolgov wrote:
>
> >> On Tue, Jul 3, 2018 at 2:57 PM Pavel Stehule <pavel.stehule@gmail.com> wrote:
> >>
> >> 2018-07-03 14:30 GMT+02:00 Nikita Glukhov <n.gluhov@postgrespro.ru>:
> >>> Attached 16th version of the patches:
> >>>   * changed type of new SQL keyword STRING
> >>>     (STRING is used as a function parameter name in Pl/Tcl tests)
> >>>   * removed implicit coercion via I/O from JSON_VALUE (see below)
> > Unfortunately, the current version of patch 0010-add-invisible-coercion-form
> > doesn't not apply anymore without conflicts, could you please rebase it?
>
> Attached 20th version of the patches rebased onto the current master.

Thank you,

Unfortunately, looks like we're in the loop "Rebase. Wait. Repeat", since the
patch again has some conflicts (this time I hope just minor conflicts). Which
is probably understandable taking into account the size of it. Maybe we need to
think about how to proceed with this, do you have any ideas?


pgsql-hackers by date:

Previous
From: Dmitry Dolgov
Date:
Subject: Re: inconsistency and inefficiency in setup_conversion()
Next
From: Dmitry Dolgov
Date:
Subject: Re: Make foo=null a warning by default.