On 10/21/19 12:44 PM, Nikita Glukhov wrote:
v39 patch is based on 5ee96b3e2221d154ffcb719bd2dee1179c53f821
Use the following git command to apply patches:
git am ~/Downloads/0001-Jsonpath-support-for-json-v39.patch
Thank you. The patch applied fine, with no errors.
Is this the type of test
On 9/27/19 9:42 PM, Nikita Glukhov wrote:
Attached 39th version of the patches rebased onto current master.
--
Nikita Glukhov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
I am unable to cleanly apply this patch.
I've tried applying to the current master (4f4061
On Tue, May 14, 2019 at 12:54 PM Andrew Alsup wrote:
> On 3/5/19 5:35 PM, Nikita Glukhov wrote:
> > Attached 36th version of the patches rebased onto jsonpath v36.
> While testing this patch a found a few issues:
>
> [1] I was not able to apply the patch to the current HEAD. However, it
> applies
Hi!
On Tue, May 14, 2019 at 3:54 AM Andrew Alsup wrote:
> array slicing [0:], [:1], and [0:1] do not work:$.c1.c2[0:].b3
>
> # select json_path_query('{"a1": 123, "b1": "xxx", "c1": {"a2": 456,
> "b2": "yyy", "c2": [{"a3": 777, "b3": "7z"},{"a3": 888, "b3":
> "8z"}]}}'::json, '$.c1.c2[0:].b3'::js
On 3/5/19 5:35 PM, Nikita Glukhov wrote:
Attached 36th version of the patches rebased onto jsonpath v36.
While testing this patch a found a few issues:
[1] I was not able to apply the patch to the current HEAD. However, it
applies cleanly to commit: e988878f85 (NOTE: I did not investigate whic
