sql: some ambiguous strict udfs should not error with null args #100928
Labels
A-sql-routine
UDFs and Stored Procedures
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
T-sql-queries
SQL Queries Team
Some record-returning UDFs return NULL or no columns (if used with SETOF) instead of returning an "ambiguous call" error.
The following logic test shows some examples and notes the expected output in postgres.
Jira issue: CRDB-26703
The text was updated successfully, but these errors were encountered: