pg_query_params Submits a command to the server and waits for the result, with the ability to pass parameters separately from the SQL command text. &reftitle.description; resourcepg_query_params resourceconnection stringquery arrayparams Submits a command to the server and waits for the result, with the ability to pass parameters separately from the SQL command text. pg_query_params is like pg_query, but offers additional functionality: parameter values can be specified separately from the command string proper. pg_query_params is supported only against PostgreSQL 7.4 or higher connections; it will fail when using earlier versions. If parameters are used, they are referred to in the query string as $1, $2, etc. params specifies the actual values of the parameters. A &null; value in this array means the corresponding parameter is SQL NULL. The primary advantage of pg_query_params over pg_query is that parameter values may be separated from the query string, thus avoiding the need for tedious and error-prone quoting and escaping. Unlike pg_query, pg_query_params allows at most one SQL command in the given string. (There can be semicolons in it, but not more than one nonempty command.) &reftitle.parameters; connection PostgreSQL database connection resource. When connection is not present, the default connection is used. The default connection is the last connection made by pg_connect or pg_pconnect. query The parameterized SQL statement. Must contain only a single statement. (multiple statements separated by semi-colons are not allowed.) If any parameters are used, they are referred to as $1, $2, etc. params An array of parameter values to substitute for the $1, $2, etc. placeholders in the original prepared query string. The number of elements in the array must match the number of placeholders. &reftitle.returnvalues; A query result resource on success&return.falseforfailure;. &reftitle.examples; ]]> &reftitle.seealso; pg_query