Re: Why is it "JSQuery"?

From: "David E(dot) Wheeler" <david(at)justatheory(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: pgsql-hackers list <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Why is it "JSQuery"?
Date: 2014-06-06 00:34:03
Message-ID: AAA3F5B1-EB86-4D21-8406-64F565241AFF@justatheory.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2014-06-06 00:37:33 Re: B-Tree support function number 3 (strxfrm() optimization)
Previous Message Andrew Dunstan 2014-06-06 00:25:43 Re: Why is it "JSQuery"?