Re: Why is it "JSQuery"? - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: Why is it "JSQuery"?
Date
Msg-id AAA3F5B1-EB86-4D21-8406-64F565241AFF@justatheory.com
Whole thread Raw
In response to Re: Why is it "JSQuery"?  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Why is it "JSQuery"?  (Oleg Bartunov <obartunov@gmail.com>)
List pgsql-hackers
On Jun 5, 2014, at 5:25 PM, Andrew Dunstan <andrew@dunslane.net> wrote:

> My understanding is that it's meant to be analogous to tsquery.
>
> At first glance, JsonPath doesn't seem to support AND and OR operators, which would make it rather less expressive
thanI gather JSQuery is meant to be. 

Yes, but perhaps it could be a superset.

I guess my real question is: Should it not be based on some existing dialect, preferably something in fairly wide use
outsidethe Postgres community? 

Unless that something is awful, of course.

David


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Why is it "JSQuery"?
Next
From: Peter Geoghegan
Date:
Subject: Re: B-Tree support function number 3 (strxfrm() optimization)