Re: Why is it "JSQuery"?

On 06/10/2014 02:46 PM, David E. Wheeler wrote:
> On Jun 10, 2014, at 12:06 PM, Oleg Bartunov <obartunov(at)gmail(dot)com> wrote:
>
>> we have many other tasks than guessing the language name.
>> jsquery is just an extension, which we invent to test our indexing
>> stuff. Eventually, it grew out. I think we'll think on better name
>> if developers agree to have it in core. For now, jsquery is good
>> enough to us.
>>
>> jsquery name doesn't need to be used at all, by the way.
>
> Yeah, I was more on about syntax than the name. We can change that any time before you release it.

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.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com