| From: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
|---|---|
| To: | Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Stas Kelvich <s(dot)kelvich(at)postgrespro(dot)ru>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, David Steele <david(at)pgmasters(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Oleg Bartunov <obartunov(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Subject: | Re: jsonpath |
| Date: | 2019-01-18 17:58:30 |
| Message-ID: | CAPpHfdsA09V3s5Q6gtCgYMmyQPOFAj7=Ez1bb7Q0eriFjJugkQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Nikita, thank you!
I noticed another thing. 3-arguments version of functions
jsonpath_exists(), jsonpath_predicate(), jsonpath_query(),
jsonpath_query_wrapped() are:
1) Not documented
2) Not used in operator definitions
3) Not used in subsequent patches
So, it looks like we can just remove then. But I think we're very
likely can commit jsonpath patch to PostgreSQL 12, but I'm not sure
about other patches. So, having those functions exposed to user can
be extremely useful until we have separate nodes for SQL/JSON. So, I
vote to document these functions.
------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-01-18 18:21:40 | More OpenBSD portability fun: getopt() fails on --option |
| Previous Message | Tom Lane | 2019-01-18 17:56:22 | Re: PSA: we lack TAP test coverage on NetBSD and OpenBSD |