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

From Oleg Bartunov
Subject Re: Why is it "JSQuery"?
Date
Msg-id CAF4Au4wvT=kuzW1WL8xFBOzn-1Wj_Sit-92QjPx5_d3q+DfKqA@mail.gmail.com
Whole thread Raw
In response to Re: Why is it "JSQuery"?  ("David E. Wheeler" <david@justatheory.com>)
Responses Re: Why is it "JSQuery"?  (Oleg Bartunov <obartunov@gmail.com>)
Re: Why is it "JSQuery"?  ("David E. Wheeler" <david@justatheory.com>)
List pgsql-hackers
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: Tom Lane
Date:
Subject: Re: Re: Getting “make: Entering an iso-8859-1 directory” error while building postgresql on MIPS platform
Next
From: Oleg Bartunov
Date:
Subject: Re: Why is it "JSQuery"?