pg_update

    (PHP 4 >= 4.3.0, PHP 5, PHP 7, PHP 8)

    pg_update — Modifica le tuple della tabella

    Descrizione

    pg_update(
        resource $connessione,
        string $nome_tabella,
        array $dati,
        array $condizione,
        int $opzioni = ?
    ): mixed

    pg_update() aggiorna le tuple che corrispondono a condizione con dati. Se opzioni è specificato, pg_convert() viene applicata su dati con le opzioni date.

    Example #1 pg_update

    <?php
    $db     = pg_connect ('dbname=foo');
    $data = array('field1'=>'AA', 'field2'=>'BB');
    // La riga seguente è sicura, date che $_POST è convertito automaticamente
    $res = pg_update($db, 'post_log', $_POST, $data);
    if (    $res) {
    echo     "Dati aggiornati: $res\n";
    }
    else {
    echo     "L'utente ha inviato dati errati\n";
    }
    ?>

    Nota:

    Questa funzione è sperimentale.

    Vedere anche pg_convert()

    Improve This Page

    Learn How To Improve This Page • Submit a Pull Request • Report a Bug
    ＋add a note

    User Contributed Notes 3 notes

    up
    2
    dominik dot bonsch at homesono dot de
    16 years ago
    Using pg_update() and pg_insert() without key validation is not secure!

    You need to check which data pairs you get, and if you want to allow to updated this column.

    Example:

    You have a table with tree colums: username, password, userlevel.

    Your users may change only their username, and their password but not their userlevel.

    If you don't filter the keys in the request array, every user can now change his userlevel just by sending a POST Request with "userlevel=>100".

    So if you don't check if the key are allowed in your request array you'll get serious sql injection vulnarabilities in your code.
    up
    -2
    jhooks
    18 years ago
    > Return Values
    >
    > Returns TRUE on success or FALSE on failure. Returns string if
    > PGSQL_DML_STRING is passed via options.

    I have found in my copy of PHP (version 4.4.0) that if you use the 'PGSQL_DML_STRING' option, the function does not execute any query. It merely returns the query which would have been executed.

    Another thing I noticed, pg_update does not seem to make use of pg_trace (atleast in 4.4.0).

    PS this isn't a bug report, just an explanation of some undocumented features I noticed. As the manual says, the function is still in development so this behaviour may differ from version to version.
    up
    -4
    sdibb at myway dot com
    19 years ago
    This function is similar to PEAR::DB's autoExecute() function, with the only difference being that the where clause is an array instead of a string.

    Also, if you want to use your instance of the DB class with this function, you can reference the existing resource connection with $db->connection.

    An example would be:
    <?
    pg_update($db->connection, $arr_update, $arr_where);
    ?>
    ＋add a note
    To Top