PG_GETRESULT(n)

πŸ“¦ version 3.1.1, in alpine 3.22, alpine 3.23, alpine 3.24, nixpkgs unstable

πŸ’– PG_GETRESULT() πŸ’–

okay bestie, welcome to the PG_GETRESULT() page from the PostgreSQL Tcl Interface Documentation ✨ This one is short, sweet, and all about checking on your async query results β€” no cap.


🌸 NAME 🌸

pg_getresult β€” process asychronous results (yes, that's the spelling on the page, bestie πŸ™ˆ).

✨ SYNOPSIS ✨

pg_getresult conn

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so pg_getresult checks to see if any commands issued by pg_sendquery have completed πŸ’….

It will return the same sort of result handle that pg_exec returns β€” iconic consistency, fr fr.

If there is no query currently being processed or all of the results have been obtained, pg_getresult returns nothing. literally nothing, bestie 😭.

πŸŽ€ ARGUMENTS πŸŽ€

  • conn β€” The handle of a connection to the database to which asynchronous requests are being issued 🫢.

πŸ‘‘ RETURN VALUE πŸ‘‘

If a query result is available, a command result object is returned. This handle can be passed to pg_result to obtain the results of the command 🌟.

If there is no query currently being processed or all of the results have been obtained, pg_getresult returns nothing. same energy as before, no cap πŸ’€.


xoxo πŸ’– β€” from the PostgreSQL Tcl Interface Documentation, dated 17 September 2020 ✨🫢

πŸ“¦ where this page comes from