Date: Wed, 6 Aug 2025 21:33:49 +0200
From: Christoph Moench-Tegeder <cmt@burggraben.net>
To: Dominique Devienne <ddevienne@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: CALL and named parameters
Message-ID: <aJOuHbxn2hIf6qDW@elch.exwg.net>
References: <CAFCRh-_iLoUtMAtyunw_-O6sgpWo04sOmB38MUVNpuQVSkL_0Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CAFCRh-_iLoUtMAtyunw_-O6sgpWo04sOmB38MUVNpuQVSkL_0Q@mail.gmail.com>
User-Agent: Mutt/2.2.14 (2025-02-20)
Archived-At: <https://www.postgresql.org/message-id/aJOuHbxn2hIf6qDW%40elch.exwg.net>
Precedence: bulk

## Dominique Devienne (ddevienne@gmail.com):

> Turns out, thanks to ChatGPT for clueing me in, CALL does NOT support
> named parameters.

Turns out, ChatGPT is once again very wrong.
As per https://www.postgresql.org/docs/14/sql-call.html ,
"Arguments can include parameter names, using the syntax name => value."
So, if you'd include what you actually did to get that error message...
And maybe try the manual, it's really good (we think).

Regards,
Christoph

-- 
Spare Space