Partial implementation of SQL/JSON path language
SQL 2016 standards among other things contains set of SQL/JSON features for
JSON processing inside of relational database. The core of SQL/JSON is JSON
path language, allowing access parts of JSON documents and make computations
over them. This commit implements partial support JSON path language as
separate datatype called "jsonpath". The implementation is partial because
it's lacking datetime support and suppression of numeric errors. Missing
features will be added later by separate commits.
Support of SQL/JSON features requires implementation of separate nodes, and it
will be considered in subsequent patches. This commit includes following
set of plain functions, allowing to execute jsonpath over jsonb values:
* jsonb_path_exists(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_match(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_query(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_query_array(jsonb, jsonpath[, jsonb, bool]).
* jsonb_path_query_first(jsonb, jsonpath[, jsonb, bool]).
This commit also implements "jsonb @? jsonpath" and "jsonb @@ jsonpath", which
are wrappers over jsonpath_exists(jsonb, jsonpath) and jsonpath_predicate(jsonb,
jsonpath) correspondingly. These operators will have an index support
(implemented in subsequent patches).
Catversion bumped, to add new functions and operators.
Code was written by Nikita Glukhov and Teodor Sigaev, revised by me.
Documentation was written by Oleg Bartunov and Liudmila Mantrova. The work
was inspired by Oleg Bartunov.
Discussion: https://postgr.es/m/fcc6fc6a-b497-f39a-923d-aa34d0c588e8%402ndQuadrant.com
Author: Nikita Glukhov, Teodor Sigaev, Alexander Korotkov, Oleg Bartunov, Liudmila Mantrova
Reviewed-by: Tomas Vondra, Andrew Dunstan, Pavel Stehule, Alexander Korotkov
2019-03-16 05:15:37 -04:00
|
|
|
/*-------------------------------------------------------------------------
|
|
|
|
|
*
|
|
|
|
|
* jsonpath.h
|
|
|
|
|
* Definitions for jsonpath datatype
|
|
|
|
|
*
|
2022-01-07 19:04:57 -05:00
|
|
|
* Copyright (c) 2019-2022, PostgreSQL Global Development Group
|
Partial implementation of SQL/JSON path language
SQL 2016 standards among other things contains set of SQL/JSON features for
JSON processing inside of relational database. The core of SQL/JSON is JSON
path language, allowing access parts of JSON documents and make computations
over them. This commit implements partial support JSON path language as
separate datatype called "jsonpath". The implementation is partial because
it's lacking datetime support and suppression of numeric errors. Missing
features will be added later by separate commits.
Support of SQL/JSON features requires implementation of separate nodes, and it
will be considered in subsequent patches. This commit includes following
set of plain functions, allowing to execute jsonpath over jsonb values:
* jsonb_path_exists(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_match(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_query(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_query_array(jsonb, jsonpath[, jsonb, bool]).
* jsonb_path_query_first(jsonb, jsonpath[, jsonb, bool]).
This commit also implements "jsonb @? jsonpath" and "jsonb @@ jsonpath", which
are wrappers over jsonpath_exists(jsonb, jsonpath) and jsonpath_predicate(jsonb,
jsonpath) correspondingly. These operators will have an index support
(implemented in subsequent patches).
Catversion bumped, to add new functions and operators.
Code was written by Nikita Glukhov and Teodor Sigaev, revised by me.
Documentation was written by Oleg Bartunov and Liudmila Mantrova. The work
was inspired by Oleg Bartunov.
Discussion: https://postgr.es/m/fcc6fc6a-b497-f39a-923d-aa34d0c588e8%402ndQuadrant.com
Author: Nikita Glukhov, Teodor Sigaev, Alexander Korotkov, Oleg Bartunov, Liudmila Mantrova
Reviewed-by: Tomas Vondra, Andrew Dunstan, Pavel Stehule, Alexander Korotkov
2019-03-16 05:15:37 -04:00
|
|
|
*
|
|
|
|
|
* IDENTIFICATION
|
|
|
|
|
* src/include/utils/jsonpath.h
|
|
|
|
|
*
|
|
|
|
|
*-------------------------------------------------------------------------
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#ifndef JSONPATH_H
|
|
|
|
|
#define JSONPATH_H
|
|
|
|
|
|
|
|
|
|
#include "fmgr.h"
|
JSON_TABLE
This feature allows jsonb data to be treated as a table and thus used in
a FROM clause like other tabular data. Data can be selected from the
jsonb using jsonpath expressions, and hoisted out of nested structures
in the jsonb to form multiple rows, more or less like an outer join.
Nikita Glukhov
Reviewers have included (in no particular order) Andres Freund, Alexander
Korotkov, Pavel Stehule, Andrew Alsup, Erik Rijkers, Zhihong Yu (whose
name I previously misspelled), Himanshu Upadhyaya, Daniel Gustafsson,
Justin Pryzby.
Discussion: https://postgr.es/m/7e2cb85d-24cf-4abb-30a5-1a33715959bd@postgrespro.ru
2022-04-04 15:36:03 -04:00
|
|
|
#include "executor/tablefunc.h"
|
Partial implementation of SQL/JSON path language
SQL 2016 standards among other things contains set of SQL/JSON features for
JSON processing inside of relational database. The core of SQL/JSON is JSON
path language, allowing access parts of JSON documents and make computations
over them. This commit implements partial support JSON path language as
separate datatype called "jsonpath". The implementation is partial because
it's lacking datetime support and suppression of numeric errors. Missing
features will be added later by separate commits.
Support of SQL/JSON features requires implementation of separate nodes, and it
will be considered in subsequent patches. This commit includes following
set of plain functions, allowing to execute jsonpath over jsonb values:
* jsonb_path_exists(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_match(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_query(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_query_array(jsonb, jsonpath[, jsonb, bool]).
* jsonb_path_query_first(jsonb, jsonpath[, jsonb, bool]).
This commit also implements "jsonb @? jsonpath" and "jsonb @@ jsonpath", which
are wrappers over jsonpath_exists(jsonb, jsonpath) and jsonpath_predicate(jsonb,
jsonpath) correspondingly. These operators will have an index support
(implemented in subsequent patches).
Catversion bumped, to add new functions and operators.
Code was written by Nikita Glukhov and Teodor Sigaev, revised by me.
Documentation was written by Oleg Bartunov and Liudmila Mantrova. The work
was inspired by Oleg Bartunov.
Discussion: https://postgr.es/m/fcc6fc6a-b497-f39a-923d-aa34d0c588e8%402ndQuadrant.com
Author: Nikita Glukhov, Teodor Sigaev, Alexander Korotkov, Oleg Bartunov, Liudmila Mantrova
Reviewed-by: Tomas Vondra, Andrew Dunstan, Pavel Stehule, Alexander Korotkov
2019-03-16 05:15:37 -04:00
|
|
|
#include "nodes/pg_list.h"
|
SQL/JSON query functions
This introduces the SQL/JSON functions for querying JSON data using
jsonpath expressions. The functions are:
JSON_EXISTS()
JSON_QUERY()
JSON_VALUE()
All of these functions only operate on jsonb. The workaround for now is
to cast the argument to jsonb.
JSON_EXISTS() tests if the jsonpath expression applied to the jsonb
value yields any values. JSON_VALUE() must return a single value, and an
error occurs if it tries to return multiple values. JSON_QUERY() must
return a json object or array, and there are various WRAPPER options for
handling scalar or multi-value results. Both these functions have
options for handling EMPTY and ERROR conditions.
Nikita Glukhov
Reviewers have included (in no particular order) Andres Freund, Alexander
Korotkov, Pavel Stehule, Andrew Alsup, Erik Rijkers, Zihong Yu,
Himanshu Upadhyaya, Daniel Gustafsson, Justin Pryzby.
Discussion: https://postgr.es/m/cd0bb935-0158-78a7-08b5-904886deac4b@postgrespro.ru
2022-03-03 13:11:14 -05:00
|
|
|
#include "nodes/primnodes.h"
|
2019-11-24 21:38:57 -05:00
|
|
|
#include "utils/jsonb.h"
|
SQL/JSON query functions
This introduces the SQL/JSON functions for querying JSON data using
jsonpath expressions. The functions are:
JSON_EXISTS()
JSON_QUERY()
JSON_VALUE()
All of these functions only operate on jsonb. The workaround for now is
to cast the argument to jsonb.
JSON_EXISTS() tests if the jsonpath expression applied to the jsonb
value yields any values. JSON_VALUE() must return a single value, and an
error occurs if it tries to return multiple values. JSON_QUERY() must
return a json object or array, and there are various WRAPPER options for
handling scalar or multi-value results. Both these functions have
options for handling EMPTY and ERROR conditions.
Nikita Glukhov
Reviewers have included (in no particular order) Andres Freund, Alexander
Korotkov, Pavel Stehule, Andrew Alsup, Erik Rijkers, Zihong Yu,
Himanshu Upadhyaya, Daniel Gustafsson, Justin Pryzby.
Discussion: https://postgr.es/m/cd0bb935-0158-78a7-08b5-904886deac4b@postgrespro.ru
2022-03-03 13:11:14 -05:00
|
|
|
#include "utils/jsonfuncs.h"
|
Partial implementation of SQL/JSON path language
SQL 2016 standards among other things contains set of SQL/JSON features for
JSON processing inside of relational database. The core of SQL/JSON is JSON
path language, allowing access parts of JSON documents and make computations
over them. This commit implements partial support JSON path language as
separate datatype called "jsonpath". The implementation is partial because
it's lacking datetime support and suppression of numeric errors. Missing
features will be added later by separate commits.
Support of SQL/JSON features requires implementation of separate nodes, and it
will be considered in subsequent patches. This commit includes following
set of plain functions, allowing to execute jsonpath over jsonb values:
* jsonb_path_exists(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_match(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_query(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_query_array(jsonb, jsonpath[, jsonb, bool]).
* jsonb_path_query_first(jsonb, jsonpath[, jsonb, bool]).
This commit also implements "jsonb @? jsonpath" and "jsonb @@ jsonpath", which
are wrappers over jsonpath_exists(jsonb, jsonpath) and jsonpath_predicate(jsonb,
jsonpath) correspondingly. These operators will have an index support
(implemented in subsequent patches).
Catversion bumped, to add new functions and operators.
Code was written by Nikita Glukhov and Teodor Sigaev, revised by me.
Documentation was written by Oleg Bartunov and Liudmila Mantrova. The work
was inspired by Oleg Bartunov.
Discussion: https://postgr.es/m/fcc6fc6a-b497-f39a-923d-aa34d0c588e8%402ndQuadrant.com
Author: Nikita Glukhov, Teodor Sigaev, Alexander Korotkov, Oleg Bartunov, Liudmila Mantrova
Reviewed-by: Tomas Vondra, Andrew Dunstan, Pavel Stehule, Alexander Korotkov
2019-03-16 05:15:37 -04:00
|
|
|
|
|
|
|
|
typedef struct
|
|
|
|
|
{
|
|
|
|
|
int32 vl_len_; /* varlena header (do not touch directly!) */
|
|
|
|
|
uint32 header; /* version and flags (see below) */
|
|
|
|
|
char data[FLEXIBLE_ARRAY_MEMBER];
|
|
|
|
|
} JsonPath;
|
|
|
|
|
|
|
|
|
|
#define JSONPATH_VERSION (0x01)
|
|
|
|
|
#define JSONPATH_LAX (0x80000000)
|
|
|
|
|
#define JSONPATH_HDRSZ (offsetof(JsonPath, data))
|
|
|
|
|
|
|
|
|
|
#define DatumGetJsonPathP(d) ((JsonPath *) DatumGetPointer(PG_DETOAST_DATUM(d)))
|
|
|
|
|
#define DatumGetJsonPathPCopy(d) ((JsonPath *) DatumGetPointer(PG_DETOAST_DATUM_COPY(d)))
|
|
|
|
|
#define PG_GETARG_JSONPATH_P(x) DatumGetJsonPathP(PG_GETARG_DATUM(x))
|
|
|
|
|
#define PG_GETARG_JSONPATH_P_COPY(x) DatumGetJsonPathPCopy(PG_GETARG_DATUM(x))
|
|
|
|
|
#define PG_RETURN_JSONPATH_P(p) PG_RETURN_POINTER(p)
|
|
|
|
|
|
2019-04-01 11:08:15 -04:00
|
|
|
#define jspIsScalar(type) ((type) >= jpiNull && (type) <= jpiBool)
|
|
|
|
|
|
Partial implementation of SQL/JSON path language
SQL 2016 standards among other things contains set of SQL/JSON features for
JSON processing inside of relational database. The core of SQL/JSON is JSON
path language, allowing access parts of JSON documents and make computations
over them. This commit implements partial support JSON path language as
separate datatype called "jsonpath". The implementation is partial because
it's lacking datetime support and suppression of numeric errors. Missing
features will be added later by separate commits.
Support of SQL/JSON features requires implementation of separate nodes, and it
will be considered in subsequent patches. This commit includes following
set of plain functions, allowing to execute jsonpath over jsonb values:
* jsonb_path_exists(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_match(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_query(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_query_array(jsonb, jsonpath[, jsonb, bool]).
* jsonb_path_query_first(jsonb, jsonpath[, jsonb, bool]).
This commit also implements "jsonb @? jsonpath" and "jsonb @@ jsonpath", which
are wrappers over jsonpath_exists(jsonb, jsonpath) and jsonpath_predicate(jsonb,
jsonpath) correspondingly. These operators will have an index support
(implemented in subsequent patches).
Catversion bumped, to add new functions and operators.
Code was written by Nikita Glukhov and Teodor Sigaev, revised by me.
Documentation was written by Oleg Bartunov and Liudmila Mantrova. The work
was inspired by Oleg Bartunov.
Discussion: https://postgr.es/m/fcc6fc6a-b497-f39a-923d-aa34d0c588e8%402ndQuadrant.com
Author: Nikita Glukhov, Teodor Sigaev, Alexander Korotkov, Oleg Bartunov, Liudmila Mantrova
Reviewed-by: Tomas Vondra, Andrew Dunstan, Pavel Stehule, Alexander Korotkov
2019-03-16 05:15:37 -04:00
|
|
|
/*
|
|
|
|
|
* All node's type of jsonpath expression
|
|
|
|
|
*/
|
|
|
|
|
typedef enum JsonPathItemType
|
|
|
|
|
{
|
|
|
|
|
jpiNull = jbvNull, /* NULL literal */
|
|
|
|
|
jpiString = jbvString, /* string literal */
|
|
|
|
|
jpiNumeric = jbvNumeric, /* numeric literal */
|
|
|
|
|
jpiBool = jbvBool, /* boolean literal: TRUE or FALSE */
|
|
|
|
|
jpiAnd, /* predicate && predicate */
|
|
|
|
|
jpiOr, /* predicate || predicate */
|
|
|
|
|
jpiNot, /* ! predicate */
|
|
|
|
|
jpiIsUnknown, /* (predicate) IS UNKNOWN */
|
|
|
|
|
jpiEqual, /* expr == expr */
|
|
|
|
|
jpiNotEqual, /* expr != expr */
|
|
|
|
|
jpiLess, /* expr < expr */
|
|
|
|
|
jpiGreater, /* expr > expr */
|
|
|
|
|
jpiLessOrEqual, /* expr <= expr */
|
|
|
|
|
jpiGreaterOrEqual, /* expr >= expr */
|
|
|
|
|
jpiAdd, /* expr + expr */
|
|
|
|
|
jpiSub, /* expr - expr */
|
|
|
|
|
jpiMul, /* expr * expr */
|
|
|
|
|
jpiDiv, /* expr / expr */
|
|
|
|
|
jpiMod, /* expr % expr */
|
|
|
|
|
jpiPlus, /* + expr */
|
|
|
|
|
jpiMinus, /* - expr */
|
|
|
|
|
jpiAnyArray, /* [*] */
|
|
|
|
|
jpiAnyKey, /* .* */
|
|
|
|
|
jpiIndexArray, /* [subscript, ...] */
|
|
|
|
|
jpiAny, /* .** */
|
|
|
|
|
jpiKey, /* .key */
|
|
|
|
|
jpiCurrent, /* @ */
|
|
|
|
|
jpiRoot, /* $ */
|
|
|
|
|
jpiVariable, /* $variable */
|
|
|
|
|
jpiFilter, /* ? (predicate) */
|
|
|
|
|
jpiExists, /* EXISTS (expr) predicate */
|
|
|
|
|
jpiType, /* .type() item method */
|
|
|
|
|
jpiSize, /* .size() item method */
|
|
|
|
|
jpiAbs, /* .abs() item method */
|
|
|
|
|
jpiFloor, /* .floor() item method */
|
|
|
|
|
jpiCeiling, /* .ceiling() item method */
|
|
|
|
|
jpiDouble, /* .double() item method */
|
Implement jsonpath .datetime() method
This commit implements jsonpath .datetime() method as it's specified in
SQL/JSON standard. There are no-argument and single-argument versions of
this method. No-argument version selects first of ISO datetime formats
matching input string. Single-argument version accepts template string as
its argument.
Additionally to .datetime() method itself this commit also implements
comparison ability of resulting date and time values. There is some difficulty
because exising jsonb_path_*() functions are immutable, while comparison of
timezoned and non-timezoned types involves current timezone. At first, current
timezone could be changes in session. Moreover, timezones themselves are not
immutable and could be updated. This is why we let existing immutable functions
throw errors on such non-immutable comparison. In the same time this commit
provides jsonb_path_*_tz() functions which are stable and support operations
involving timezones. As new functions are added to the system catalog,
catversion is bumped.
Support of .datetime() method was the only blocker prevents T832 from being
marked as supported. sql_features.txt is updated correspondingly.
Extracted from original patch by Nikita Glukhov, Teodor Sigaev, Oleg Bartunov.
Heavily revised by me. Comments were adjusted by Liudmila Mantrova.
Discussion: https://postgr.es/m/fcc6fc6a-b497-f39a-923d-aa34d0c588e8%402ndQuadrant.com
Discussion: https://postgr.es/m/CAPpHfdsZgYEra_PeCLGNoXOWYx6iU-S3wF8aX0ObQUcZU%2B4XTw%40mail.gmail.com
Author: Alexander Korotkov, Nikita Glukhov, Teodor Sigaev, Oleg Bartunov, Liudmila Mantrova
Reviewed-by: Anastasia Lubennikova, Peter Eisentraut
2019-09-25 14:54:14 -04:00
|
|
|
jpiDatetime, /* .datetime() item method */
|
Partial implementation of SQL/JSON path language
SQL 2016 standards among other things contains set of SQL/JSON features for
JSON processing inside of relational database. The core of SQL/JSON is JSON
path language, allowing access parts of JSON documents and make computations
over them. This commit implements partial support JSON path language as
separate datatype called "jsonpath". The implementation is partial because
it's lacking datetime support and suppression of numeric errors. Missing
features will be added later by separate commits.
Support of SQL/JSON features requires implementation of separate nodes, and it
will be considered in subsequent patches. This commit includes following
set of plain functions, allowing to execute jsonpath over jsonb values:
* jsonb_path_exists(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_match(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_query(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_query_array(jsonb, jsonpath[, jsonb, bool]).
* jsonb_path_query_first(jsonb, jsonpath[, jsonb, bool]).
This commit also implements "jsonb @? jsonpath" and "jsonb @@ jsonpath", which
are wrappers over jsonpath_exists(jsonb, jsonpath) and jsonpath_predicate(jsonb,
jsonpath) correspondingly. These operators will have an index support
(implemented in subsequent patches).
Catversion bumped, to add new functions and operators.
Code was written by Nikita Glukhov and Teodor Sigaev, revised by me.
Documentation was written by Oleg Bartunov and Liudmila Mantrova. The work
was inspired by Oleg Bartunov.
Discussion: https://postgr.es/m/fcc6fc6a-b497-f39a-923d-aa34d0c588e8%402ndQuadrant.com
Author: Nikita Glukhov, Teodor Sigaev, Alexander Korotkov, Oleg Bartunov, Liudmila Mantrova
Reviewed-by: Tomas Vondra, Andrew Dunstan, Pavel Stehule, Alexander Korotkov
2019-03-16 05:15:37 -04:00
|
|
|
jpiKeyValue, /* .keyvalue() item method */
|
|
|
|
|
jpiSubscript, /* array subscript: 'expr' or 'expr TO expr' */
|
|
|
|
|
jpiLast, /* LAST array subscript */
|
|
|
|
|
jpiStartsWith, /* STARTS WITH predicate */
|
|
|
|
|
jpiLikeRegex, /* LIKE_REGEX predicate */
|
|
|
|
|
} JsonPathItemType;
|
|
|
|
|
|
|
|
|
|
/* XQuery regex mode flags for LIKE_REGEX predicate */
|
|
|
|
|
#define JSP_REGEX_ICASE 0x01 /* i flag, case insensitive */
|
Fix bogus handling of XQuery regex option flags.
The SQL spec defers to XQuery to define what the option flags are
for LIKE_REGEX patterns. XQuery says that:
* 's' allows the dot character to match newlines, which by
default it will not;
* 'm' allows ^ and $ to match at newlines, not only at the
start/end of the whole string.
Thus, these are *not* inverses as they are for the similarly-named
POSIX options, and neither one corresponds to the POSIX 'n' option.
Fortunately, Spencer's library does expose these two behaviors as
separately twiddlable flags, so we just have to fix the mapping from
JSP flag bits to REG flag bits. I also chose to rename the symbol
for 's' to DOTALL, to make it clearer that it's not the inverse
of MLINE.
Also, XQuery says that if the 'q' flag "is used together with the m, s,
or x flag, that flag has no effect". I read this as saying that 'q'
overrides the other flags; whoever wrote our code seems to have read
it backwards.
Lastly, while XQuery's 'x' flag is related to what Spencer's code
does for REG_EXPANDED, it's not the same or a subset. It seems best
to treat XQuery's 'x' as unimplemented for now. Maybe later we can
expand our regex code to offer 'x'-style parsing as a separate option.
While at it, refactor the jsonpath code so that (a) there's only
one copy of the flag transformation logic not two, and (b) the
processing of flags is independent of the order in which the flags
are written.
We need some documentation updates to go with this, but I'll
tackle that separately.
Back-patch to v12 where this code originated.
Discussion: https://postgr.es/m/CAPpHfdvDci4iqNF9fhRkTqhe-5_8HmzeLt56drH%2B_Rv2rNRqfg@mail.gmail.com
Reference: https://www.w3.org/TR/2017/REC-xpath-functions-31-20170321/#flags
2019-09-17 15:39:51 -04:00
|
|
|
#define JSP_REGEX_DOTALL 0x02 /* s flag, dot matches newline */
|
|
|
|
|
#define JSP_REGEX_MLINE 0x04 /* m flag, ^/$ match at newlines */
|
|
|
|
|
#define JSP_REGEX_WSPACE 0x08 /* x flag, ignore whitespace in pattern */
|
2019-06-19 15:40:58 -04:00
|
|
|
#define JSP_REGEX_QUOTE 0x10 /* q flag, no special characters */
|
Partial implementation of SQL/JSON path language
SQL 2016 standards among other things contains set of SQL/JSON features for
JSON processing inside of relational database. The core of SQL/JSON is JSON
path language, allowing access parts of JSON documents and make computations
over them. This commit implements partial support JSON path language as
separate datatype called "jsonpath". The implementation is partial because
it's lacking datetime support and suppression of numeric errors. Missing
features will be added later by separate commits.
Support of SQL/JSON features requires implementation of separate nodes, and it
will be considered in subsequent patches. This commit includes following
set of plain functions, allowing to execute jsonpath over jsonb values:
* jsonb_path_exists(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_match(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_query(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_query_array(jsonb, jsonpath[, jsonb, bool]).
* jsonb_path_query_first(jsonb, jsonpath[, jsonb, bool]).
This commit also implements "jsonb @? jsonpath" and "jsonb @@ jsonpath", which
are wrappers over jsonpath_exists(jsonb, jsonpath) and jsonpath_predicate(jsonb,
jsonpath) correspondingly. These operators will have an index support
(implemented in subsequent patches).
Catversion bumped, to add new functions and operators.
Code was written by Nikita Glukhov and Teodor Sigaev, revised by me.
Documentation was written by Oleg Bartunov and Liudmila Mantrova. The work
was inspired by Oleg Bartunov.
Discussion: https://postgr.es/m/fcc6fc6a-b497-f39a-923d-aa34d0c588e8%402ndQuadrant.com
Author: Nikita Glukhov, Teodor Sigaev, Alexander Korotkov, Oleg Bartunov, Liudmila Mantrova
Reviewed-by: Tomas Vondra, Andrew Dunstan, Pavel Stehule, Alexander Korotkov
2019-03-16 05:15:37 -04:00
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Support functions to parse/construct binary value.
|
|
|
|
|
* Unlike many other representation of expression the first/main
|
|
|
|
|
* node is not an operation but left operand of expression. That
|
2019-05-26 08:58:18 -04:00
|
|
|
* allows to implement cheap follow-path descending in jsonb
|
Partial implementation of SQL/JSON path language
SQL 2016 standards among other things contains set of SQL/JSON features for
JSON processing inside of relational database. The core of SQL/JSON is JSON
path language, allowing access parts of JSON documents and make computations
over them. This commit implements partial support JSON path language as
separate datatype called "jsonpath". The implementation is partial because
it's lacking datetime support and suppression of numeric errors. Missing
features will be added later by separate commits.
Support of SQL/JSON features requires implementation of separate nodes, and it
will be considered in subsequent patches. This commit includes following
set of plain functions, allowing to execute jsonpath over jsonb values:
* jsonb_path_exists(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_match(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_query(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_query_array(jsonb, jsonpath[, jsonb, bool]).
* jsonb_path_query_first(jsonb, jsonpath[, jsonb, bool]).
This commit also implements "jsonb @? jsonpath" and "jsonb @@ jsonpath", which
are wrappers over jsonpath_exists(jsonb, jsonpath) and jsonpath_predicate(jsonb,
jsonpath) correspondingly. These operators will have an index support
(implemented in subsequent patches).
Catversion bumped, to add new functions and operators.
Code was written by Nikita Glukhov and Teodor Sigaev, revised by me.
Documentation was written by Oleg Bartunov and Liudmila Mantrova. The work
was inspired by Oleg Bartunov.
Discussion: https://postgr.es/m/fcc6fc6a-b497-f39a-923d-aa34d0c588e8%402ndQuadrant.com
Author: Nikita Glukhov, Teodor Sigaev, Alexander Korotkov, Oleg Bartunov, Liudmila Mantrova
Reviewed-by: Tomas Vondra, Andrew Dunstan, Pavel Stehule, Alexander Korotkov
2019-03-16 05:15:37 -04:00
|
|
|
* structure and then execute operator with right operand
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
typedef struct JsonPathItem
|
|
|
|
|
{
|
|
|
|
|
JsonPathItemType type;
|
|
|
|
|
|
|
|
|
|
/* position form base to next node */
|
|
|
|
|
int32 nextPos;
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* pointer into JsonPath value to current node, all positions of current
|
|
|
|
|
* are relative to this base
|
|
|
|
|
*/
|
|
|
|
|
char *base;
|
|
|
|
|
|
|
|
|
|
union
|
|
|
|
|
{
|
|
|
|
|
/* classic operator with two operands: and, or etc */
|
|
|
|
|
struct
|
|
|
|
|
{
|
|
|
|
|
int32 left;
|
|
|
|
|
int32 right;
|
|
|
|
|
} args;
|
|
|
|
|
|
|
|
|
|
/* any unary operation */
|
|
|
|
|
int32 arg;
|
|
|
|
|
|
|
|
|
|
/* storage for jpiIndexArray: indexes of array */
|
|
|
|
|
struct
|
|
|
|
|
{
|
|
|
|
|
int32 nelems;
|
|
|
|
|
struct
|
|
|
|
|
{
|
|
|
|
|
int32 from;
|
|
|
|
|
int32 to;
|
|
|
|
|
} *elems;
|
|
|
|
|
} array;
|
|
|
|
|
|
|
|
|
|
/* jpiAny: levels */
|
|
|
|
|
struct
|
|
|
|
|
{
|
|
|
|
|
uint32 first;
|
|
|
|
|
uint32 last;
|
|
|
|
|
} anybounds;
|
|
|
|
|
|
|
|
|
|
struct
|
|
|
|
|
{
|
|
|
|
|
char *data; /* for bool, numeric and string/key */
|
|
|
|
|
int32 datalen; /* filled only for string/key */
|
|
|
|
|
} value;
|
|
|
|
|
|
|
|
|
|
struct
|
|
|
|
|
{
|
|
|
|
|
int32 expr;
|
|
|
|
|
char *pattern;
|
|
|
|
|
int32 patternlen;
|
|
|
|
|
uint32 flags;
|
|
|
|
|
} like_regex;
|
|
|
|
|
} content;
|
|
|
|
|
} JsonPathItem;
|
|
|
|
|
|
|
|
|
|
#define jspHasNext(jsp) ((jsp)->nextPos > 0)
|
|
|
|
|
|
|
|
|
|
extern void jspInit(JsonPathItem *v, JsonPath *js);
|
|
|
|
|
extern void jspInitByBuffer(JsonPathItem *v, char *base, int32 pos);
|
|
|
|
|
extern bool jspGetNext(JsonPathItem *v, JsonPathItem *a);
|
|
|
|
|
extern void jspGetArg(JsonPathItem *v, JsonPathItem *a);
|
|
|
|
|
extern void jspGetLeftArg(JsonPathItem *v, JsonPathItem *a);
|
|
|
|
|
extern void jspGetRightArg(JsonPathItem *v, JsonPathItem *a);
|
|
|
|
|
extern Numeric jspGetNumeric(JsonPathItem *v);
|
|
|
|
|
extern bool jspGetBool(JsonPathItem *v);
|
|
|
|
|
extern char *jspGetString(JsonPathItem *v, int32 *len);
|
|
|
|
|
extern bool jspGetArraySubscript(JsonPathItem *v, JsonPathItem *from,
|
|
|
|
|
JsonPathItem *to, int i);
|
SQL/JSON query functions
This introduces the SQL/JSON functions for querying JSON data using
jsonpath expressions. The functions are:
JSON_EXISTS()
JSON_QUERY()
JSON_VALUE()
All of these functions only operate on jsonb. The workaround for now is
to cast the argument to jsonb.
JSON_EXISTS() tests if the jsonpath expression applied to the jsonb
value yields any values. JSON_VALUE() must return a single value, and an
error occurs if it tries to return multiple values. JSON_QUERY() must
return a json object or array, and there are various WRAPPER options for
handling scalar or multi-value results. Both these functions have
options for handling EMPTY and ERROR conditions.
Nikita Glukhov
Reviewers have included (in no particular order) Andres Freund, Alexander
Korotkov, Pavel Stehule, Andrew Alsup, Erik Rijkers, Zihong Yu,
Himanshu Upadhyaya, Daniel Gustafsson, Justin Pryzby.
Discussion: https://postgr.es/m/cd0bb935-0158-78a7-08b5-904886deac4b@postgrespro.ru
2022-03-03 13:11:14 -05:00
|
|
|
extern bool jspIsMutable(JsonPath *path, List *varnames, List *varexprs);
|
Partial implementation of SQL/JSON path language
SQL 2016 standards among other things contains set of SQL/JSON features for
JSON processing inside of relational database. The core of SQL/JSON is JSON
path language, allowing access parts of JSON documents and make computations
over them. This commit implements partial support JSON path language as
separate datatype called "jsonpath". The implementation is partial because
it's lacking datetime support and suppression of numeric errors. Missing
features will be added later by separate commits.
Support of SQL/JSON features requires implementation of separate nodes, and it
will be considered in subsequent patches. This commit includes following
set of plain functions, allowing to execute jsonpath over jsonb values:
* jsonb_path_exists(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_match(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_query(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_query_array(jsonb, jsonpath[, jsonb, bool]).
* jsonb_path_query_first(jsonb, jsonpath[, jsonb, bool]).
This commit also implements "jsonb @? jsonpath" and "jsonb @@ jsonpath", which
are wrappers over jsonpath_exists(jsonb, jsonpath) and jsonpath_predicate(jsonb,
jsonpath) correspondingly. These operators will have an index support
(implemented in subsequent patches).
Catversion bumped, to add new functions and operators.
Code was written by Nikita Glukhov and Teodor Sigaev, revised by me.
Documentation was written by Oleg Bartunov and Liudmila Mantrova. The work
was inspired by Oleg Bartunov.
Discussion: https://postgr.es/m/fcc6fc6a-b497-f39a-923d-aa34d0c588e8%402ndQuadrant.com
Author: Nikita Glukhov, Teodor Sigaev, Alexander Korotkov, Oleg Bartunov, Liudmila Mantrova
Reviewed-by: Tomas Vondra, Andrew Dunstan, Pavel Stehule, Alexander Korotkov
2019-03-16 05:15:37 -04:00
|
|
|
|
|
|
|
|
extern const char *jspOperationName(JsonPathItemType type);
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Parsing support data structures.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
typedef struct JsonPathParseItem JsonPathParseItem;
|
|
|
|
|
|
|
|
|
|
struct JsonPathParseItem
|
|
|
|
|
{
|
|
|
|
|
JsonPathItemType type;
|
|
|
|
|
JsonPathParseItem *next; /* next in path */
|
|
|
|
|
|
|
|
|
|
union
|
|
|
|
|
{
|
|
|
|
|
|
|
|
|
|
/* classic operator with two operands: and, or etc */
|
|
|
|
|
struct
|
|
|
|
|
{
|
|
|
|
|
JsonPathParseItem *left;
|
|
|
|
|
JsonPathParseItem *right;
|
|
|
|
|
} args;
|
|
|
|
|
|
|
|
|
|
/* any unary operation */
|
|
|
|
|
JsonPathParseItem *arg;
|
|
|
|
|
|
|
|
|
|
/* storage for jpiIndexArray: indexes of array */
|
|
|
|
|
struct
|
|
|
|
|
{
|
|
|
|
|
int nelems;
|
|
|
|
|
struct
|
|
|
|
|
{
|
|
|
|
|
JsonPathParseItem *from;
|
|
|
|
|
JsonPathParseItem *to;
|
|
|
|
|
} *elems;
|
|
|
|
|
} array;
|
|
|
|
|
|
|
|
|
|
/* jpiAny: levels */
|
|
|
|
|
struct
|
|
|
|
|
{
|
|
|
|
|
uint32 first;
|
|
|
|
|
uint32 last;
|
|
|
|
|
} anybounds;
|
|
|
|
|
|
|
|
|
|
struct
|
|
|
|
|
{
|
|
|
|
|
JsonPathParseItem *expr;
|
|
|
|
|
char *pattern; /* could not be not null-terminated */
|
|
|
|
|
uint32 patternlen;
|
|
|
|
|
uint32 flags;
|
|
|
|
|
} like_regex;
|
|
|
|
|
|
|
|
|
|
/* scalars */
|
|
|
|
|
Numeric numeric;
|
|
|
|
|
bool boolean;
|
|
|
|
|
struct
|
|
|
|
|
{
|
|
|
|
|
uint32 len;
|
|
|
|
|
char *val; /* could not be not null-terminated */
|
|
|
|
|
} string;
|
|
|
|
|
} value;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
typedef struct JsonPathParseResult
|
|
|
|
|
{
|
|
|
|
|
JsonPathParseItem *expr;
|
|
|
|
|
bool lax;
|
|
|
|
|
} JsonPathParseResult;
|
|
|
|
|
|
|
|
|
|
extern JsonPathParseResult *parsejsonpath(const char *str, int len);
|
|
|
|
|
|
Fix bogus handling of XQuery regex option flags.
The SQL spec defers to XQuery to define what the option flags are
for LIKE_REGEX patterns. XQuery says that:
* 's' allows the dot character to match newlines, which by
default it will not;
* 'm' allows ^ and $ to match at newlines, not only at the
start/end of the whole string.
Thus, these are *not* inverses as they are for the similarly-named
POSIX options, and neither one corresponds to the POSIX 'n' option.
Fortunately, Spencer's library does expose these two behaviors as
separately twiddlable flags, so we just have to fix the mapping from
JSP flag bits to REG flag bits. I also chose to rename the symbol
for 's' to DOTALL, to make it clearer that it's not the inverse
of MLINE.
Also, XQuery says that if the 'q' flag "is used together with the m, s,
or x flag, that flag has no effect". I read this as saying that 'q'
overrides the other flags; whoever wrote our code seems to have read
it backwards.
Lastly, while XQuery's 'x' flag is related to what Spencer's code
does for REG_EXPANDED, it's not the same or a subset. It seems best
to treat XQuery's 'x' as unimplemented for now. Maybe later we can
expand our regex code to offer 'x'-style parsing as a separate option.
While at it, refactor the jsonpath code so that (a) there's only
one copy of the flag transformation logic not two, and (b) the
processing of flags is independent of the order in which the flags
are written.
We need some documentation updates to go with this, but I'll
tackle that separately.
Back-patch to v12 where this code originated.
Discussion: https://postgr.es/m/CAPpHfdvDci4iqNF9fhRkTqhe-5_8HmzeLt56drH%2B_Rv2rNRqfg@mail.gmail.com
Reference: https://www.w3.org/TR/2017/REC-xpath-functions-31-20170321/#flags
2019-09-17 15:39:51 -04:00
|
|
|
extern int jspConvertRegexFlags(uint32 xflags);
|
|
|
|
|
|
SQL/JSON query functions
This introduces the SQL/JSON functions for querying JSON data using
jsonpath expressions. The functions are:
JSON_EXISTS()
JSON_QUERY()
JSON_VALUE()
All of these functions only operate on jsonb. The workaround for now is
to cast the argument to jsonb.
JSON_EXISTS() tests if the jsonpath expression applied to the jsonb
value yields any values. JSON_VALUE() must return a single value, and an
error occurs if it tries to return multiple values. JSON_QUERY() must
return a json object or array, and there are various WRAPPER options for
handling scalar or multi-value results. Both these functions have
options for handling EMPTY and ERROR conditions.
Nikita Glukhov
Reviewers have included (in no particular order) Andres Freund, Alexander
Korotkov, Pavel Stehule, Andrew Alsup, Erik Rijkers, Zihong Yu,
Himanshu Upadhyaya, Daniel Gustafsson, Justin Pryzby.
Discussion: https://postgr.es/m/cd0bb935-0158-78a7-08b5-904886deac4b@postgrespro.ru
2022-03-03 13:11:14 -05:00
|
|
|
/*
|
|
|
|
|
* Evaluation of jsonpath
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
/* External variable passed into jsonpath. */
|
|
|
|
|
typedef struct JsonPathVariableEvalContext
|
|
|
|
|
{
|
|
|
|
|
char *name;
|
|
|
|
|
Oid typid;
|
|
|
|
|
int32 typmod;
|
|
|
|
|
struct ExprContext *econtext;
|
|
|
|
|
struct ExprState *estate;
|
JSON_TABLE
This feature allows jsonb data to be treated as a table and thus used in
a FROM clause like other tabular data. Data can be selected from the
jsonb using jsonpath expressions, and hoisted out of nested structures
in the jsonb to form multiple rows, more or less like an outer join.
Nikita Glukhov
Reviewers have included (in no particular order) Andres Freund, Alexander
Korotkov, Pavel Stehule, Andrew Alsup, Erik Rijkers, Zhihong Yu (whose
name I previously misspelled), Himanshu Upadhyaya, Daniel Gustafsson,
Justin Pryzby.
Discussion: https://postgr.es/m/7e2cb85d-24cf-4abb-30a5-1a33715959bd@postgrespro.ru
2022-04-04 15:36:03 -04:00
|
|
|
MemoryContext mcxt; /* memory context for cached value */
|
SQL/JSON query functions
This introduces the SQL/JSON functions for querying JSON data using
jsonpath expressions. The functions are:
JSON_EXISTS()
JSON_QUERY()
JSON_VALUE()
All of these functions only operate on jsonb. The workaround for now is
to cast the argument to jsonb.
JSON_EXISTS() tests if the jsonpath expression applied to the jsonb
value yields any values. JSON_VALUE() must return a single value, and an
error occurs if it tries to return multiple values. JSON_QUERY() must
return a json object or array, and there are various WRAPPER options for
handling scalar or multi-value results. Both these functions have
options for handling EMPTY and ERROR conditions.
Nikita Glukhov
Reviewers have included (in no particular order) Andres Freund, Alexander
Korotkov, Pavel Stehule, Andrew Alsup, Erik Rijkers, Zihong Yu,
Himanshu Upadhyaya, Daniel Gustafsson, Justin Pryzby.
Discussion: https://postgr.es/m/cd0bb935-0158-78a7-08b5-904886deac4b@postgrespro.ru
2022-03-03 13:11:14 -05:00
|
|
|
Datum value;
|
|
|
|
|
bool isnull;
|
|
|
|
|
bool evaluated;
|
|
|
|
|
} JsonPathVariableEvalContext;
|
|
|
|
|
|
|
|
|
|
/* SQL/JSON item */
|
|
|
|
|
extern void JsonItemFromDatum(Datum val, Oid typid, int32 typmod,
|
|
|
|
|
JsonbValue *res);
|
|
|
|
|
|
|
|
|
|
extern bool JsonPathExists(Datum jb, JsonPath *path, List *vars, bool *error);
|
|
|
|
|
extern Datum JsonPathQuery(Datum jb, JsonPath *jp, JsonWrapper wrapper,
|
|
|
|
|
bool *empty, bool *error, List *vars);
|
|
|
|
|
extern JsonbValue *JsonPathValue(Datum jb, JsonPath *jp, bool *empty,
|
|
|
|
|
bool *error, List *vars);
|
|
|
|
|
|
|
|
|
|
extern int EvalJsonPathVar(void *vars, char *varName, int varNameLen,
|
|
|
|
|
JsonbValue *val, JsonbValue *baseObject);
|
|
|
|
|
|
2022-04-08 08:16:38 -04:00
|
|
|
extern PGDLLIMPORT const TableFuncRoutine JsonbTableRoutine;
|
JSON_TABLE
This feature allows jsonb data to be treated as a table and thus used in
a FROM clause like other tabular data. Data can be selected from the
jsonb using jsonpath expressions, and hoisted out of nested structures
in the jsonb to form multiple rows, more or less like an outer join.
Nikita Glukhov
Reviewers have included (in no particular order) Andres Freund, Alexander
Korotkov, Pavel Stehule, Andrew Alsup, Erik Rijkers, Zhihong Yu (whose
name I previously misspelled), Himanshu Upadhyaya, Daniel Gustafsson,
Justin Pryzby.
Discussion: https://postgr.es/m/7e2cb85d-24cf-4abb-30a5-1a33715959bd@postgrespro.ru
2022-04-04 15:36:03 -04:00
|
|
|
|
Partial implementation of SQL/JSON path language
SQL 2016 standards among other things contains set of SQL/JSON features for
JSON processing inside of relational database. The core of SQL/JSON is JSON
path language, allowing access parts of JSON documents and make computations
over them. This commit implements partial support JSON path language as
separate datatype called "jsonpath". The implementation is partial because
it's lacking datetime support and suppression of numeric errors. Missing
features will be added later by separate commits.
Support of SQL/JSON features requires implementation of separate nodes, and it
will be considered in subsequent patches. This commit includes following
set of plain functions, allowing to execute jsonpath over jsonb values:
* jsonb_path_exists(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_match(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_query(jsonb, jsonpath[, jsonb, bool]),
* jsonb_path_query_array(jsonb, jsonpath[, jsonb, bool]).
* jsonb_path_query_first(jsonb, jsonpath[, jsonb, bool]).
This commit also implements "jsonb @? jsonpath" and "jsonb @@ jsonpath", which
are wrappers over jsonpath_exists(jsonb, jsonpath) and jsonpath_predicate(jsonb,
jsonpath) correspondingly. These operators will have an index support
(implemented in subsequent patches).
Catversion bumped, to add new functions and operators.
Code was written by Nikita Glukhov and Teodor Sigaev, revised by me.
Documentation was written by Oleg Bartunov and Liudmila Mantrova. The work
was inspired by Oleg Bartunov.
Discussion: https://postgr.es/m/fcc6fc6a-b497-f39a-923d-aa34d0c588e8%402ndQuadrant.com
Author: Nikita Glukhov, Teodor Sigaev, Alexander Korotkov, Oleg Bartunov, Liudmila Mantrova
Reviewed-by: Tomas Vondra, Andrew Dunstan, Pavel Stehule, Alexander Korotkov
2019-03-16 05:15:37 -04:00
|
|
|
#endif
|