On 31.03.23 16:57, Nikita Malakhov wrote:
Sorry to bother, but there is a question on JsonPath - how many bits in
the JsonPath
header could be used for the version? The JsonPath header is 4 bytes,
and currently
the Version part is defined as
#define JSONPATH_VERSION (0x01)
I don't know the
Hi!
Sorry to bother, but there is a question on JsonPath - how many bits in the
JsonPath
header could be used for the version? The JsonPath header is 4 bytes, and
currently
the Version part is defined as
#define JSONPATH_VERSION (0x01)
Thanks!
On Sun, Mar 5, 2023 at 6:55 PM Peter Eisentraut <
On 03.03.23 21:16, Dean Rasheed wrote:
I think this new feature ought to be mentioned in the docs somewhere.
Perhaps a sentence or two in the note below table 9.49 would suffice,
since it looks like that's where jsonpath numbers are mentioned for
the first time.
Done. I actually put it into
On Tue, 28 Feb 2023 at 07:44, Peter Eisentraut
wrote:
>
> Attached is a patch to add nondecimal integer literals and underscores
> in numeric literals to the SQL JSON path language. This matches the
> recent additions to the core SQL syntax. It follows ECMAScript in
> combination with the
On 28.02.23 01:09, Vik Fearing wrote:
On 2/27/23 20:13, Peter Eisentraut wrote:
Attached is a patch to add nondecimal integer literals and underscores
in numeric literals to the SQL JSON path language. This matches the
recent additions to the core SQL syntax. It follows ECMAScript in
On 2/27/23 20:13, Peter Eisentraut wrote:
Attached is a patch to add nondecimal integer literals and underscores
in numeric literals to the SQL JSON path language. This matches the
recent additions to the core SQL syntax. It follows ECMAScript in
combination with the current SQL draft.
of jsonpath goes through
numeric_in, which already supports all this, so this patch is just a bit
of lexer work and some tests.From abeefa990231dea398ddd923d9e992e0ad945159 Mon Sep 17 00:00:00 2001
From: Peter Eisentraut
Date: Mon, 27 Feb 2023 19:27:32 +0100
Subject: [PATCH v1] SQL JSON path
