PG_SENDQUERY_PREPARED(n)

✨ NAME ✨

pg_sendquery_prepared — send a request to execute a prepared statement to the backend connection, without waiting for a result. okay so bestie, this page is brought to you by the PostgreSQL Tcl Interface Documentation, and yes we're doing this 💅.

🎀 SYNOPSIS 🎀

pg_sendquery_prepared conn statementName [args]

No cap, that's the whole call — slay. ✨

💅 DESCRIPTION 💅

pg_sendquery_prepared submits a command to the PostgreSQL server. It works like pg_exec, except that it does not return a result. Instead, the command is issued to the backend asynchronously — it's giving main character energy, but that's literally what the manpage says, not me adding lore.

The result is either an error message or nothing. An empty return indicates that the command was dispatched to the backend. So if you get nothing back, that does not mean the vibes are off; it means the command got sent. 🫶

🌸 ARGUMENTS 🌸

• conn — the handle of the connection on which to execute the command.
• statementName — the name of the prepared SQL statement to execute asynchronously.
• args — consists of zero or more optional values that can be inserted, unquoted, into the SQL statement using $-style substitution. iykyk, keep that unquoted detail in mind.

🦋 RETURN VALUE 🦋

A Tcl error will be returned if pgtcl was unable to issue the command. Otherwise, an empty string will be returned. It is up to the developer to use pg_getresult to obtain results from commands issued with pg_sendquery. yes, pg_sendquery — that's what the page says, so we're keeping it exactly like that, bestie. 💖

quick vibe check: empty string back = command was dispatched; Tcl error = pgtcl couldn't issue it. The actual results are a whole separate quest via pg_getresult 🌈.

mwah 💌 — signed off by the PostgreSQL Tcl Interface Documentation, footer source/version PG_SEND...PREPARED(), dated 17 September 2020. periodt. 🫶✨