Re: SQL/JSON path issues/questions
От | Alexander Korotkov |
---|---|
Тема | Re: SQL/JSON path issues/questions |
Дата | |
Msg-id | CAPpHfdtuvD8H_pHe87hHoz+ZVwP=VTHVk=X8idnB5tejHCjYqQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: SQL/JSON path issues/questions (Thom Brown <thom@linux.com>) |
Список | pgsql-hackers |
On Thu, Jun 27, 2019 at 4:57 PM Thom Brown <thom@linux.com> wrote: > On Wed, 19 Jun 2019 at 20:04, Alexander Korotkov > <a.korotkov@postgrespro.ru> wrote: > > On Wed, Jun 19, 2019 at 7:07 PM Thom Brown <thom@linux.com> wrote: > > > On Thu, 13 Jun 2019 at 14:59, Thom Brown <thom@linux.com> wrote: > > > Also, this example doesn't work: > > > > > > '$.track ? (@.segments[*] ? (@.HR > 130)).segments.size()' > > > > > > This gives me: > > > > > > psql: ERROR: syntax error, unexpected $end at end of jsonpath input > > > LINE 13: }','$.track ? (@.segments[*]'); > > > ^ > > > > Perhaps it should be following: > > > > '$.track ? (exists(@.segments[*] ? (@.HR > 130))).segments.size()' > > I'm not clear on why the original example doesn't work here. It doesn't work because filter expression should be predicate, i.e. always return bool. In the original example filter expression selects some json elements. My original idea was that it was accidentally come from some of our extensions where we've allowed that. But it appears to be just plain wrong example, which never worked. Sorry for that. ------ Alexander Korotkov Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
В списке pgsql-hackers по дате отправления: