Re: Why is it "JSQuery"?

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: "David E(dot) Wheeler" <david(at)justatheory(dot)com>, Oleg Bartunov <obartunov(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Why is it "JSQuery"?
Date: 2014-06-15 21:07:31
Message-ID: 539E0B13.1020200@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 06/15/2014 04:58 PM, Josh Berkus wrote:
> I've been poking at the various json-query syntaxes you forwarded, and
> none of them really work for the actual jsquery features. Also, the
> existing syntax has the advantage of being *simple*, relatively
> speaking, and reasonably similar to JSONPATH.
>
> In other words, what I'm saying is: I don't think there's an existing,
> poplular syntax we could reasonably use.
>

Not to mention the similarity to tsquery, which is something not to be
despised.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Maxence Ahlouche 2014-06-15 22:01:15 Re: [GSoC] Clustering in MADlib - status update
Previous Message Josh Berkus 2014-06-15 20:58:18 Re: Why is it "JSQuery"?