Hi,
On 2/24/19 10:03 AM, Alexander Korotkov wrote:
> Hi!
>
> Attached is revised version of jsonpath. Assuming that jsonpath have
> problem places, I decided to propose partial implementation.
> Following functionality was cut from jsonpath:
> 1) Support of datetime datatypes. Besides error suppression, this
> functionality have troubles with timezones. According to standard we
> should support timezones in jsonpath expressions. But that would
> prevent jsonpath functions from being immutable, that in turn limits
> their usage in expression indexes.
Assuming we get the patch committed without the datetime stuff now, what
does that mean for the future? Does that mean we'll be unable to extend
it to support datetime in the future, or what? If we define the jsonpath
functions as immutable now, people may create indexes - which means we
won't be able to downgrade it to stable later.
So, what's the plan here? The only thing I can think of is having two
sets of functions - an immutable one, prohibiting datetime expressions,
and stable that can't be used for indexes etc.
> 2) Suppression of numeric errors. I will post it as a separate patch.
> Pushing this even this partial implementation of jsonpath to PG 12 is
> still very useful. Also it will simplify a lot pushing other parts of
> SQL/JSON to future releases.
>
+1 to push at least partial (but still useful) subset, instead of just
bumping the patch to PG13
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services