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

From Oleg Bartunov
Subject Re: Why is it "JSQuery"?
Date
Msg-id CAF4Au4y0o65rCcQaUozXD1jEQUKDnRpicg+peFfRY1X-CLPKCw@mail.gmail.com
Whole thread Raw
In response to Re: Why is it "JSQuery"?  (Oleg Bartunov <obartunov@gmail.com>)
List pgsql-hackers
The closest problem we have is jsonb statistics (lack of, actually) ,
which prevents use of all the power of jsquery. I hope Jan Urbański
could work on this.

Oleg

On Tue, Jun 10, 2014 at 11:06 PM, Oleg Bartunov <obartunov@gmail.com> wrote:
> People,
>
> 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.
>
> Oleg
>
> On Tue, Jun 10, 2014 at 10:04 PM, David E. Wheeler
> <david@justatheory.com> wrote:
>> On Jun 6, 2014, at 3:50 PM, Josh Berkus <josh@agliodbs.com> wrote:
>>
>>> Maybe we should call it "jsonesque"  ;-)
>>
>> I propose JOQL: JSON Object Query Language.
>>
>> Best,
>>
>> David
>>
>> PS: JAQL sounds better, but [already exists](http://code.google.com/p/jaql/).



pgsql-hackers by date:

Previous
From: Oleg Bartunov
Date:
Subject: Re: Why is it "JSQuery"?
Next
From: "Brightwell, Adam"
Date:
Subject: Re: API change advice: Passing plan invalidation info from the rewriter into the planner?