From: | Oleg Bartunov <obartunov(at)gmail(dot)com> |
---|---|
To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Jan Urbański <wulczer(at)wulczer(dot)org> |
Subject: | Re: Why is it "JSQuery"? |
Date: | 2014-06-10 19:31:31 |
Message-ID: | CAF4Au4y0o65rCcQaUozXD1jEQUKDnRpicg+peFfRY1X-CLPKCw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)gmail(dot)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(at)justatheory(dot)com> wrote:
>> On Jun 6, 2014, at 3:50 PM, Josh Berkus <josh(at)agliodbs(dot)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/).
From | Date | Subject | |
---|---|---|---|
Next Message | Brightwell, Adam | 2014-06-10 20:28:24 | Re: API change advice: Passing plan invalidation info from the rewriter into the planner? |
Previous Message | Oleg Bartunov | 2014-06-10 19:06:35 | Re: Why is it "JSQuery"? |