Re: Why is it "JSQuery"?

From: "David E(dot) Wheeler" <david(at)justatheory(dot)com>
To: Oleg Bartunov <obartunov(at)gmail(dot)com>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Why is it "JSQuery"?
Date: 2014-06-10 21:46:19
Message-ID: 22529FD8-1254-4E60-B85D-0FA91AB3B01A@justatheory.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Vik Fearing 2014-06-10 22:21:58 Re: "RETURNING PRIMARY KEY" syntax extension
Previous Message Brian Dunavant 2014-06-10 21:29:13 Question about partial functional indexes and the query planner