parameters to be passed to the function; they must match the declared
function argument list. When the <parameter>isint</> field of a
parameter structure is true, the <parameter>u.integer</> value is sent
- to the server as an integer of the indicated length (this must be 1,
- 2, or 4 bytes); proper byte-swapping occurs. When <parameter>isint</>
+ to the server as an integer of the indicated length (this must be
+ 2 or 4 bytes); proper byte-swapping occurs. When <parameter>isint</>
is false, the indicated number of bytes at <parameter>*u.ptr</> are
sent with no processing; the data must be in the format expected by
the server for binary transmission of the function's argument data
- type. <parameter>result_buf</parameter> is the buffer in which to
- place the return value. The caller must have allocated sufficient
+ type. (The declaration of <parameter>u.ptr</> as being of
+ type <type>int *</> is historical; it would be better to consider
+ it <type>void *</>.)
+ <parameter>result_buf</parameter> points to the buffer in which to place
+ the function's return value. The caller must have allocated sufficient
space to store the return value. (There is no check!) The actual result
- length will be returned in the integer pointed to by
- <parameter>result_len</parameter>. If a 1, 2, or 4-byte integer result
+ length in bytes will be returned in the integer pointed to by
+ <parameter>result_len</parameter>. If a 2- or 4-byte integer result
is expected, set <parameter>result_is_int</parameter> to 1, otherwise
set it to 0. Setting <parameter>result_is_int</parameter> to 1 causes
<application>libpq</> to byte-swap the value if necessary, so that it
- is delivered as a proper <type>int</type> value for the client machine.
+ is delivered as a proper <type>int</type> value for the client machine;
+ note that a 4-byte integer is delivered into <parameter>*result_buf</>
+ for either allowed result size.
When <parameter>result_is_int</> is 0, the binary-format byte string
- sent by the server is returned unmodified.
+ sent by the server is returned unmodified. (In this case it's better
+ to consider <parameter>result_buf</parameter> as being of
+ type <type>void *</>.)
</para>
<para>
* PQfn - Send a function call to the POSTGRES backend.
*
* conn : backend connection
- * fnid : function id
- * result_buf : pointer to result buffer (&int if integer)
- * result_len : length of return value.
- * actual_result_len: actual length returned. (differs from result_len
- * for varlena structures.)
- * result_type : If the result is an integer, this must be 1,
+ * fnid : OID of function to be called
+ * result_buf : pointer to result buffer
+ * result_len : actual length of result is returned here
+ * result_is_int : If the result is an integer, this must be 1,
* otherwise this should be 0
- * args : pointer to an array of function arguments.
+ * args : pointer to an array of function arguments
* (each has length, if integer, and value/pointer)
* nargs : # of arguments in args array.
*
* RETURNS
* PGresult with status = PGRES_COMMAND_OK if successful.
- * *actual_result_len is > 0 if there is a return value, 0 if not.
+ * *result_len is > 0 if there is a return value, 0 if not.
* PGresult with status = PGRES_FATAL_ERROR if backend returns an error.
* NULL on communications failure. conn->errorMessage will be set.
* ----------------
PQfn(PGconn *conn,
int fnid,
int *result_buf,
- int *actual_result_len,
+ int *result_len,
int result_is_int,
const PQArgBlock *args,
int nargs)
{
- *actual_result_len = 0;
+ *result_len = 0;
if (!conn)
return NULL;
if (PG_PROTOCOL_MAJOR(conn->pversion) >= 3)
return pqFunctionCall3(conn, fnid,
- result_buf, actual_result_len,
+ result_buf, result_len,
result_is_int,
args, nargs);
else
return pqFunctionCall2(conn, fnid,
- result_buf, actual_result_len,
+ result_buf, result_len,
result_is_int,
args, nargs);
}