Re: Avoiding possible future conformance headaches in JSON work - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Avoiding possible future conformance headaches in JSON work
Date
Msg-id 19567.1568934846@sss.pgh.pa.us
Whole thread Raw
In response to Re: Avoiding possible future conformance headaches in JSON work  (Chapman Flack <chap@anastigmatix.net>)
Responses Re: Avoiding possible future conformance headaches in JSON work
List pgsql-hackers
Chapman Flack <chap@anastigmatix.net> writes:
> Sure, against *every* non-spec feature we have or ever will have, someone
> /could/ raise a generic "what if SQL committee might add something pretty
> similar in future".
> But what we have in this case are specific non-spec features (array, map,
> and sequence constructors, lambdas, map/fold/reduce, user-defined
> functions) that are flat-out already present in the current version of
> the language that the SQL committee is clearly modeling jsonpath on.

Sure.  But we also modeled those features on the same language that the
committee is looking at (or at least I sure hope we did).  So it's
reasonable to assume that they would come out at the same spot without
any prompting.  And we can prompt them ;-).

            regards, tom lane



pgsql-hackers by date:

Previous
From: Chapman Flack
Date:
Subject: Re: Avoiding possible future conformance headaches in JSON work
Next
From: Ashwin Agrawal
Date:
Subject: Re: Syntax highlighting for Postgres spec files