On Fri, Mar 28, 2025 at 7:12 PM Евгений Горбанев <gorbanyo...@basealt.ru> wrote: > If you replace is_not_null with NOT NULL in the query, everything works > correctly. > It seems that is_not_null is an incorrect keyword and it should not be > used, but I don't understand how it gets here.
It seems what happens is that internally in gram.y (~line 14274), the DefElem for the not-null option is assigned the name "is_not_null". As a result, this allows users to explicitly use "is_not_null" as the option name. However, the value provided for the is_not_null option in this way might not be a Boolean as expected, which triggers the assertion. I kind of doubt we should allow the use of the "is_not_null" keyword in the xmltable function. Hi Álvaro, what do you think about this? Thanks Richard
