Re: CALL and named parameters - Mailing list pgsql-general

From David G. Johnston
Subject Re: CALL and named parameters
Date
Msg-id CAKFQuwaGO-pmBVc2Vk9vwmbkhNpxHeZM77=oCtG+Duoc-G58cg@mail.gmail.com
Whole thread Raw
In response to Re: CALL and named parameters  (Dominique Devienne <ddevienne@gmail.com>)
Responses Re: CALL and named parameters
Re: CALL and named parameters
Re: CALL and named parameters
List pgsql-general
On Thursday, August 7, 2025, Dominique Devienne <ddevienne@gmail.com> wrote:

What's not nice is in the way it failed IMHO. I guess I persist it's
not a user friendly message :)

Then write the error message you would have liked to see.
 

Can you overload a function solely by changing an argument name?

No, the signature is only the name and input argument types.
 
If not, as I suspect, then function lookup doesn't strictly depend on
argument names (like in C++).
So the function did exist, with the correct "signature" (ignoring
argument names).
And I was "just" using the wrong arg-name. That tripped me up.

How is it “just” an argument name when you are using named argument syntax?

David J.

pgsql-general by date:

Previous
From: Dominique Devienne
Date:
Subject: Re: CALL and named parameters
Next
From: Pavel Stehule
Date:
Subject: Re: CALL and named parameters