Re: Variable substitution in jsonb functions fails for jsonpath operator like_regex

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Erwin Brandstetter <brsaweda(at)gmail(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Variable substitution in jsonb functions fails for jsonpath operator like_regex
Date: 2023-10-18 21:16:10
Message-ID: 3157573.1697663770@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Erwin Brandstetter <brsaweda(at)gmail(dot)com> writes:
> The functions jsonb_path_exists() and friends accept a "vars" parameter for
> parameter substitution in the jsonpath argument. This seems to work for all
> jsonpath operators except "like_regex":

> SELECT * FROM tbl
> WHERE jsonb_path_exists(data, '$[*].value ? (@ like_regex $foo)', '{"foo":
> "CEO"}');

>> ERROR: syntax error at or near "$foo" of jsonpath input
>> LINE 3: WHERE jsonb_path_exists(data, '$[*].value ? (@ like_regex $...

> Notably, the same works even for "starts with":

Hmm, maybe just an oversight in jsonpath_gram.y?

predicate:
...
| expr STARTS_P WITH_P starts_with_initial
| expr LIKE_REGEX_P STRING_P
| expr LIKE_REGEX_P STRING_P FLAG_P STRING_P
;

starts_with_initial:
STRING_P { $$ = makeItemString(&$1); }
| VARIABLE_P { $$ = makeItemVariable(&$1); }
;

Maybe it wouldn't take more than s/STRING_P/starts_with_initial/
here (though I'd then rename starts_with_initial to something
more generic). With bad luck there might be some dependency on
this restriction downstream of the grammar, but I suspect not.
Didn't try though.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jeff Janes 2023-10-19 00:42:21 Re: Variable substitution in jsonb functions fails for jsonpath operator like_regex
Previous Message Tom Lane 2023-10-18 20:25:39 Re: pg_dump needs SELECT privileges on irrelevant extension table