| From: | Oleg Bartunov <obartunov(at)gmail(dot)com> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers list <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Why is it "JSQuery"? |
| Date: | 2014-06-06 13:54:53 |
| Message-ID: | CAF4Au4whQrQajoueyBmWrEz6Kpm6zg9r1BAAxf6Opov=2fx4jg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jsquery - is QUERY language, JsonPath - is language to EXTRACT json parts.
On Fri, Jun 6, 2014 at 4:34 AM, David E. Wheeler <david(at)justatheory(dot)com> wrote:
> On Jun 5, 2014, at 5:25 PM, Andrew Dunstan <andrew(at)dunslane(dot)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 than I 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 outside the Postgres community?
>
> Unless that something is awful, of course.
>
> David
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2014-06-06 16:12:13 | Re: Why is it "JSQuery"? |
| Previous Message | Gurjeet Singh | 2014-06-06 12:01:09 | Re: Proposing pg_hibernate |