Re: [HACKERS] SQL/JSON in PostgreSQL

2018-03-01 Thread Andres Freund
On 2018-03-02 10:31:34 +0300, Oleg Bartunov wrote: > Right, we divided it to manageable pieces as Andrew suggested. Please close the corresponding CF entry next time, if you do so. It's a bit painful having to reconstruct such things out of numerous large threads. Greetings, Andres Freund

Re: [HACKERS] SQL/JSON in PostgreSQL

2018-03-01 Thread Oleg Bartunov
On 2 Mar 2018 09:44, "Andres Freund" wrote: Hi, This patchset currently has multiple CF entries: https://commitfest.postgresql.org/17/1063/ and then subordinate ones like https://commitfest.postgresql.org/17/1471/ https://commitfest.postgresql.org/17/1472/ https://commitfest.postgresql.org/17/1

Re: [HACKERS] SQL/JSON in PostgreSQL

2018-03-01 Thread Andres Freund
Hi, This patchset currently has multiple CF entries: https://commitfest.postgresql.org/17/1063/ and then subordinate ones like https://commitfest.postgresql.org/17/1471/ https://commitfest.postgresql.org/17/1472/ https://commitfest.postgresql.org/17/1473/ Thus I'm marking this entry as returned

Re: [HACKERS] SQL/JSON in PostgreSQL

2018-01-10 Thread Oleg Bartunov
On 10 Jan 2018 20:14, "Andrew Dunstan" wrote: On 01/10/2018 01:37 AM, Oleg Bartunov wrote: > > > > this. Something similar to what we're using for json itself (a > simple lexer and a recursive descent parser) would be more > suitable. > > > flex/bison is right tool for jsonp

Re: [HACKERS] SQL/JSON in PostgreSQL

2018-01-10 Thread Andrew Dunstan
On 01/10/2018 01:37 AM, Oleg Bartunov wrote: > > > >     this. Something similar to what we're using for json itself (a >     simple lexer and a recursive descent parser) would be more > suitable. > > > flex/bison is right tool for jsonpath, which is complex thing.  It's not really

Re: [HACKERS] SQL/JSON in PostgreSQL

2018-01-09 Thread Oleg Bartunov
On 9 Jan 2018 23:44, "Andrew Dunstan" wrote: On 01/02/2018 05:23 PM, Andrew Dunstan wrote: > > On 01/02/2018 05:04 PM, Nikita Glukhov wrote: >> I have removed all extra features from the patch set, they can be >> found in our >> github repository: >> https://github.com/postgrespro/sqljson/tree/

Re: [HACKERS] SQL/JSON in PostgreSQL

2018-01-09 Thread Pavel Stehule
2018-01-09 21:44 GMT+01:00 Andrew Dunstan : > > > On 01/02/2018 05:23 PM, Andrew Dunstan wrote: > > > > On 01/02/2018 05:04 PM, Nikita Glukhov wrote: > >> I have removed all extra features from the patch set, they can be > >> found in our > >> github repository: > >> https://github.com/postgrespro

Re: [HACKERS] SQL/JSON in PostgreSQL

2018-01-09 Thread Andrew Dunstan
On 01/02/2018 05:23 PM, Andrew Dunstan wrote: > > On 01/02/2018 05:04 PM, Nikita Glukhov wrote: >> I have removed all extra features from the patch set, they can be >> found in our >> github repository: >> https://github.com/postgrespro/sqljson/tree/sqljson_ext. >> >> Now there are 10 patches whi

Re: [HACKERS] SQL/JSON in PostgreSQL

2018-01-06 Thread Nikita Glukhov
On 07.01.2018 00:11, Pavel Stehule wrote: 2018-01-06 22:02 GMT+01:00 Oleg Bartunov >: On Sat, Jan 6, 2018 at 8:22 AM, Pavel Stehule mailto:pavel.steh...@gmail.com>> wrote: > Hi > > I am checking the JSONPath related code > > Questions, not

Re: [HACKERS] SQL/JSON in PostgreSQL

2018-01-06 Thread Nikita Glukhov
On 07.01.2018 00:33, Pavel Stehule wrote: 2018-01-06 22:23 GMT+01:00 Nikita Glukhov >: On 07.01.2018 00:22, Pavel Stehule wrote: Hi I try jsonpath on json {     "book":     [     {     "title": "Beginning JSON",

Re: [HACKERS] SQL/JSON in PostgreSQL

2018-01-06 Thread Pavel Stehule
2018-01-06 22:23 GMT+01:00 Nikita Glukhov : > On 07.01.2018 00:22, Pavel Stehule wrote: > > Hi > > I try jsonpath on json > > { > "book": > [ > { > "title": "Beginning JSON", > "author": "Ben Smith", > "price": 49.99 > }, > > { >

Re: [HACKERS] SQL/JSON in PostgreSQL

2018-01-06 Thread Nikita Glukhov
On 07.01.2018 00:22, Pavel Stehule wrote: Hi I try jsonpath on json {     "book":     [     {     "title": "Beginning JSON",     "author": "Ben Smith",     "price": 49.99     },     {     "title": "JSON at Work",     "author": "Tom Marrs",  

Re: [HACKERS] SQL/JSON in PostgreSQL

2018-01-06 Thread Pavel Stehule
Hi I try jsonpath on json { "book": [ { "title": "Beginning JSON", "author": "Ben Smith", "price": 49.99 }, { "title": "JSON at Work", "author": "Tom Marrs", "price": 29.99 },

Re: [HACKERS] SQL/JSON in PostgreSQL

2018-01-06 Thread Pavel Stehule
2018-01-06 22:02 GMT+01:00 Oleg Bartunov : > On Sat, Jan 6, 2018 at 8:22 AM, Pavel Stehule > wrote: > > Hi > > > > I am checking the JSONPath related code > > > > Questions, notes: > > > > 1. jsonpath operators are not consistent with any other .. json, xml .. > I am > > missing ?, @> operátors >

Re: [HACKERS] SQL/JSON in PostgreSQL

2018-01-06 Thread Oleg Bartunov
On Sat, Jan 6, 2018 at 8:22 AM, Pavel Stehule wrote: > Hi > > I am checking the JSONPath related code > > Questions, notes: > > 1. jsonpath operators are not consistent with any other .. json, xml .. I am > missing ?, @> operátors I have slides about jsonpath http://www.sai.msu.su/~megera/postgre

Re: [HACKERS] SQL/JSON in PostgreSQL

2018-01-05 Thread Pavel Stehule
Hi I am checking the JSONPath related code Questions, notes: 1. jsonpath operators are not consistent with any other .. json, xml .. I am missing ?, @> operátors 2. documentation issue - there is "'{"a":[1,2,3,4,5]}'::json *? '$.a[*] ? (@ > 2)'" - operator *? doesn't exists 3. operator @~ looks

Re: [HACKERS] SQL/JSON in PostgreSQL

2018-01-05 Thread Pavel Stehule
2018-01-03 17:04 GMT+01:00 Oleg Bartunov : > > > On 3 Jan 2018 00:23, "Andrew Dunstan" > wrote: > > > > On 01/02/2018 05:04 PM, Nikita Glukhov wrote: > > > > I have removed all extra features from the patch set, they can be > > found in our > > github repository: > > https://github.com/postgrespr

Re: [HACKERS] SQL/JSON in PostgreSQL

2018-01-04 Thread Pavel Stehule
I have removed all extra features from the patch set, they can be found in our > github repository: https://github.com/postgrespro/sqljson/tree/sqljson_ext > . > > Now there are 10 patches which have the following dependencies: > > 1: > 2: 1 > 3: 2 > 4: 2 > 5: > 6: > 7: 2, 5, 6 > 8: 7, 4 > 9: 7 >

Re: [HACKERS] SQL/JSON in PostgreSQL

2018-01-03 Thread Andrew Dunstan
On 01/03/2018 11:04 AM, Oleg Bartunov wrote: > > > On 3 Jan 2018 00:23, "Andrew Dunstan" > wrote: > > > > On 01/02/2018 05:04 PM, Nikita Glukhov wrote: > > > > I have removed all extra features from the patch set, they can be > > found in ou

Re: [HACKERS] SQL/JSON in PostgreSQL

2018-01-03 Thread Oleg Bartunov
On 3 Jan 2018 00:23, "Andrew Dunstan" wrote: On 01/02/2018 05:04 PM, Nikita Glukhov wrote: > > I have removed all extra features from the patch set, they can be > found in our > github repository: > https://github.com/postgrespro/sqljson/tree/sqljson_ext. > > Now there are 10 patches which have

Re: [HACKERS] SQL/JSON in PostgreSQL

2018-01-02 Thread Andrew Dunstan
On 01/02/2018 05:04 PM, Nikita Glukhov wrote: > > I have removed all extra features from the patch set, they can be > found in our > github repository: > https://github.com/postgrespro/sqljson/tree/sqljson_ext. > > Now there are 10 patches which have the following dependencies: > > 1: > 2: 1 > 3:

Re: [HACKERS] SQL/JSON in PostgreSQL

2018-01-02 Thread Oleg Bartunov
On Tue, Jan 2, 2018 at 8:39 PM, Andrew Dunstan wrote: > > > On 01/02/2018 02:44 PM, Oleg Bartunov wrote: >> On Tue, Jan 2, 2018 at 10:47 AM, Pavel Stehule >> wrote: > >>> I am looking on this patch set and it looks very well. >>> >>> Personally I dislike any extensions against SQL/JSON in this p

Re: [HACKERS] SQL/JSON in PostgreSQL

2018-01-02 Thread Andrew Dunstan
On 01/02/2018 03:48 PM, Pavel Stehule wrote: > > > 2018-01-02 21:39 GMT+01:00 Andrew Dunstan > mailto:andrew.duns...@2ndquadrant.com>>: > > > > On 01/02/2018 02:44 PM, Oleg Bartunov wrote: > > On Tue, Jan 2, 2018 at 10:47 AM, Pavel Stehule > mailto:pavel.steh...@gmail.com>> wrote: > >

Re: [HACKERS] SQL/JSON in PostgreSQL

2018-01-02 Thread Pavel Stehule
2018-01-02 21:39 GMT+01:00 Andrew Dunstan : > > > On 01/02/2018 02:44 PM, Oleg Bartunov wrote: > > On Tue, Jan 2, 2018 at 10:47 AM, Pavel Stehule > wrote: > > >> I am looking on this patch set and it looks very well. > >> > >> Personally I dislike any extensions against SQL/JSON in this patch. An

Re: [HACKERS] SQL/JSON in PostgreSQL

2018-01-02 Thread Andrew Dunstan
On 01/02/2018 02:44 PM, Oleg Bartunov wrote: > On Tue, Jan 2, 2018 at 10:47 AM, Pavel Stehule > wrote: >> I am looking on this patch set and it looks very well. >> >> Personally I dislike any extensions against SQL/JSON in this patch. And >> there is lot of extensions there. It doesn't mean so

Re: [HACKERS] SQL/JSON in PostgreSQL

2018-01-02 Thread Oleg Bartunov
On Tue, Jan 2, 2018 at 10:47 AM, Pavel Stehule wrote: > > > 2018-01-02 3:04 GMT+01:00 Nikita Glukhov : >> >> On 29.11.2017 05:24, Michael Paquier wrote: >> >>> On Wed, Nov 15, 2017 at 10:17 AM, Nikita Glukhov >>> wrote: Attached the new version of the patches where displaying of SQL/JSO

Re: [HACKERS] SQL/JSON in PostgreSQL

2018-01-02 Thread Pavel Stehule
Hi regress tests fails Regards Pavel regression.diffs Description: Binary data

Re: [HACKERS] SQL/JSON in PostgreSQL

2018-01-02 Thread Pavel Stehule
2018-01-02 3:04 GMT+01:00 Nikita Glukhov : > On 29.11.2017 05:24, Michael Paquier wrote: > > On Wed, Nov 15, 2017 at 10:17 AM, Nikita Glukhov >> wrote: >> >>> Attached the new version of the patches where displaying of SQL/JSON >>> constructor nodes was fixed. I decided not to invent new nodes b

Re: [HACKERS] SQL/JSON in PostgreSQL

2018-01-02 Thread Pavel Stehule
2018-01-02 3:04 GMT+01:00 Nikita Glukhov : > On 29.11.2017 05:24, Michael Paquier wrote: > > On Wed, Nov 15, 2017 at 10:17 AM, Nikita Glukhov >> wrote: >> >>> Attached the new version of the patches where displaying of SQL/JSON >>> constructor nodes was fixed. I decided not to invent new nodes b

Re: [HACKERS] SQL/JSON in PostgreSQL

2017-11-28 Thread Michael Paquier
On Wed, Nov 15, 2017 at 10:17 AM, Nikita Glukhov wrote: > Attached the new version of the patches where displaying of SQL/JSON > constructor nodes was fixed. I decided not to invent new nodes but to > extend > existing FuncExpr, Aggref, WindowFunc nodes with new formatting fields that > give us a