You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Tom Lane 83a5641945 Provide more-specific error details/hints for function lookup failures. ... Up to now we've contented ourselves with a one-size-fits-all error hint when we fail to find any match to a function or procedure call. That was mostly okay in the beginning, but it was never great, and since the introduction of named arguments it's really not adequate. We at least ought to distinguish "function name doesn't exist" from "function name exists, but not with those argument names". And the rules for named-argument matching are arcane enough that some more detail seems warranted if we match the argument names but the call still doesn't work. This patch creates a framework for dealing with these problems: FuncnameGetCandidates and related code will now pass back a bitmask of flags showing how far the match succeeded. This allows a considerable amount of granularity in the reports. The set-bits-in-a-bitmask approach means that when there are multiple candidate functions, the report will reflect the match(es) that got the furthest, which seems correct. Also, we can avoid mentioning "maybe add casts" unless failure to match argument types is actually the issue. Extend the same return-a-bitmask approach to OpernameGetCandidates. The issues around argument names don't apply to operator syntax, but it still seems worth distinguishing between "there is no operator of that name" and "we couldn't match the argument types". While at it, adjust these messages and related ones to more strictly separate "detail" from "hint", following our message style guidelines' distinction between those. Reported-by: Dominique Devienne <ddevienne@gmail.com> Author: Tom Lane <tgl@sss.pgh.pa.us> Reviewed-by: Robert Haas <robertmhaas@gmail.com> Discussion: https://postgr.es/m/1756041.1754616558@sss.pgh.pa.us		3 months ago
..
plpython_call.out	plpython: Remove regression test infrastructure for Python 2.	4 years ago
plpython_composite.out	Fix recursive RECORD-returning plpython functions.	2 years ago
plpython_do.out	plpython: Remove regression test infrastructure for Python 2.	4 years ago
plpython_drop.out	plpython: Remove regression test infrastructure for Python 2.	4 years ago
plpython_ereport.out	Fix a couple of typos	3 years ago
plpython_error.out	Provide more-specific error details/hints for function lookup failures.	3 months ago
plpython_global.out	plpython: Remove regression test infrastructure for Python 2.	4 years ago
plpython_import.out	plpython: Remove regression test infrastructure for Python 2.	4 years ago
plpython_newline.out	plpython: Remove regression test infrastructure for Python 2.	4 years ago
plpython_params.out	plpython: Remove regression test infrastructure for Python 2.	4 years ago
plpython_populate.out	…
plpython_quote.out	plpython: Remove regression test infrastructure for Python 2.	4 years ago
plpython_record.out	plpython: Remove regression test infrastructure for Python 2.	4 years ago
plpython_schema.out	…
plpython_setof.out	plpython: Add test for returning Python set from SETOF function	9 months ago
plpython_spi.out	Simplify some SPI tests of PL/Python	1 year ago
plpython_subtransaction.out	plpython: Remove regression test infrastructure for Python 2.	4 years ago
plpython_test.out	plpython: Remove regression test infrastructure for Python 2.	4 years ago
plpython_transaction.out	plpython: Remove regression test infrastructure for Python 2.	4 years ago
plpython_trigger.out	PL/Python: Add event trigger support	4 months ago
plpython_types.out	Tighten array dimensionality checks in Python -> SQL array conversion.	3 years ago
plpython_unicode.out	plpython: Remove regression test infrastructure for Python 2.	4 years ago
plpython_void.out	plpython: Remove regression test infrastructure for Python 2.	4 years ago