Re: Why is it "JSQuery"?

Поиск
Список
Период
Сортировка
От David E. Wheeler
Тема Re: Why is it "JSQuery"?
Дата
Msg-id AAA3F5B1-EB86-4D21-8406-64F565241AFF@justatheory.com
обсуждение исходный текст
Ответ на Re: Why is it "JSQuery"?  (Andrew Dunstan <andrew@dunslane.net>)
Ответы Re: Why is it "JSQuery"?  (Oleg Bartunov <obartunov@gmail.com>)
Список pgsql-hackers
On Jun 5, 2014, at 5:25 PM, Andrew Dunstan <andrew@dunslane.net> wrote:

> My understanding is that it's meant to be analogous to tsquery.
>
> At first glance, JsonPath doesn't seem to support AND and OR operators, which would make it rather less expressive
thanI gather JSQuery is meant to be. 

Yes, but perhaps it could be a superset.

I guess my real question is: Should it not be based on some existing dialect, preferably something in fairly wide use
outsidethe Postgres community? 

Unless that something is awful, of course.

David


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Andrew Dunstan
Дата:
Сообщение: Re: Why is it "JSQuery"?
Следующее
От: Peter Geoghegan
Дата:
Сообщение: Re: B-Tree support function number 3 (strxfrm() optimization)