pg_update
(PHP 4 >= 4.3.0, PHP 5, PHP 7)
pg_update — Update table
Description
$connection
, string $table_name
, array $data
, array $condition
[, int $options = PGSQL_DML_EXEC
] ) : mixedpg_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.
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_ASYNCorPGSQL_DML_STRINGcombined. IfPGSQL_DML_STRINGis part of theoptionsthen query string is returned. WhenPGSQL_DML_NO_CONVorPGSQL_DML_ESCAPEis set, it does not call pg_convert() internally.
Return Values
Returns TRUE on success or FALSE on failure. Returns string if PGSQL_DML_STRING is passed
via options.
Examples
Example #1 pg_update() example
<?php
$db = pg_connect('dbname=foo');
$data = array('field1'=>'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";
}
?>
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.
|
English translation
You have asked to visit this site in English. For now, only the interface is translated, but not all the content yet.If you want to help me in translations, your contribution is welcome. All you need to do is register on the site, and send me a message asking me to add you to the group of translators, which will give you the opportunity to translate the pages you want. A link at the bottom of each translated page indicates that you are the translator, and has a link to your profile.
Thank you in advance.
Document created the 30/01/2003, last modified the 26/10/2018
Source of the printed document:https://www.gaudry.be/en/php-rf-pg-update.html
The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.
References
These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.
