pg_update
Update table
&reftitle.description;
mixedpg_update
resourceconnection
stringtable_name
arraydata
arraycondition
intoptionsPGSQL_DML_EXEC
pg_update updates records that matches
condition with data. If
options is specified,
pg_convert is applied to
data with specified options.
pg_update updates records specified by
assoc_array which has
field=>value.
If options is specified,
pg_convert is applied to
assoc_array with the specified flags.
By default pg_update passes raw values. Values
must be escaped or PGSQL_DML_ESCAPE option must be
specified. PGSQL_DML_ESCAPE quotes and escapes
paramters/identifiers. Therefore, table/column names became case
sensitive.
Note that neither escape nor prepared query can protect LIKE query,
JSON, Array, Regex, etc. These parameters should be handled
according to their contexts. i.e. Escape/validate values.
&reftitle.parameters;
connection
PostgreSQL database connection resource.
table_name
Name of the table into which to update rows.
data
An array whose keys are field names in the table table_name,
and whose values are what matched rows are to be updated to.
condition
An array whose keys are field names in the table table_name,
and whose values are the conditions that a row must meet to be updated.
options
Any number of PGSQL_CONV_FORCE_NULL,
PGSQL_DML_NO_CONV,
PGSQL_DML_ESCAPE,
PGSQL_DML_EXEC,
PGSQL_DML_ASYNC or
PGSQL_DML_STRING combined. If PGSQL_DML_STRING is part of the
options then query string is returned. When PGSQL_DML_NO_CONV
or PGSQL_DML_ESCAPE is set, it does not call pg_convert internally.
&reftitle.returnvalues;
&return.success; Returns string if PGSQL_DML_STRING is passed
via options.
&reftitle.examples;
<function>pg_update</function> example
'AA', 'field2'=>'BB');
// This is safe somewhat, since all values are escaped.
// However PostgreSQL supports JSON/Array. These are not
// safe by nither escape nor prepared query.
$res = pg_update($db, 'post_log', $_POST, $data);
if ($res) {
echo "Data is updated: $res\n";
} else {
echo "User must have sent wrong inputs\n";
}
?>
]]>
&reftitle.changelog;
&Version;
&Description;
5.6.0
No longer experimental. Added PGSQL_DML_ESCAPE constant,
&true;/&false; and &null; data type support.
5.5.3/5.4.19
Direct SQL injection to table_name and Indirect
SQL injection to identifiers are fixed.
&reftitle.seealso;
pg_convert