pg-affected-rows () only runs on the LAST SQL STATEMENT executed. If you compound several statements together then pg_affected_rows might not return what you expect.
For example:
<?php
$result = pg_query ('BEGIN; INSERT INTO foo (bar) VALUES (\'baz\'; COMMIT');
echo (pg_affected_rows ($result));
?>
will cause 0 to be printed, because the last statement executed by Postgres was COMMIT, which doesn't affect any rows.
I haven't tried this so am not certain it works, but you SHOULD be able to get the row counts you want if you split your queries up.
For example:
<?php
$result = pg_query ('BEGIN; INSERT INTO foo (bar) VALUES (\'baz\';');
echo (pg_affected_rows ($result));
pg_query ('COMMIT;');
?>
should allow you to get the number of rows affected by the previous query. I haven't tried this yet though, so don't count on it.
pg_affected_rows
(PHP 4 >= 4.2.0, PHP 5, PHP 7, PHP 8)
pg_affected_rows — Devuelve el número de registros afectados (filas)
Descripción
pg_affected_rows() Devuelve el número de filas
(casos/registros/filas) afectadas por consultas de tipo INSERT,
UPDATE, y
DELETE.
Desde PostgreSQL 9.0 y superior, el servidor devuelve el número de filas seleccionadas. Las versiones más antiguas de PostgreSQL devuelven 0 para SELECT.
Nota:
Esta función se llamaba pg_cmdtuples().
Parámetros
-
result -
El recurso de resultados de la consulta PostgreSQL o PostgreSQL query result resource, es devuelto por pg_query(), pg_query_params() o pg_execute() (entre otros).
Valores devueltos
El número de filas afectadas por la consulta. Si no hay filas afectadas devolverá 0 (cero).
Ejemplos
Ejemplo #1 Ejemplo de pg_affected_rows()
<?php
$result = pg_query($conn, "INSERT INTO authors VALUES ('Orwell', 2002, 'Animal Farm')");
$cmdtuples = pg_affected_rows($result);
echo "filas que han sido afectadas: " . $cmdtuples ;
?>El resultado del ejemplo sería:
filas que han sido afectadas: 1.
Ver también
- pg_query() - Ejecutar una consulta
- 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
- pg_execute() - Envía una solicitud para ejecutar una setencia preparada con parámetros dados, y espera el resultado
- pg_num_rows() - Returns the number of rows in a result
add a note
User Contributed Notes 5 notes
Anonymous ¶
17 years ago
Bruno Baguette ¶
19 years ago
Note that when you submit several SQL queries, within one BEGIN;COMMIT; like this one :
$SQLQuery = 'BEGIN;';
$SQLQuery.= 'INSERT INTO a (a,b) VALUES (1,2);';
$SQLQuery.= 'INSERT INTO b (ref_b,c) VALUES (2,5);';
$SQLQuery.= 'COMMIT;';
$HandleResults = pg_query($SQLQuery);
echo(pg_affected_rows($HandleResults));
pg_affected_rows() will return 0
Anonymous ¶
16 years ago
There is something called auto-commit, when you supply more than one query delimited by ; semicolon all-or-none is done if one fails. No need for BEGIN;COMMIT;ROLLBACK when doing one query. its logic to mee pg_affected_rows() returns affected rows and if you want to do 2 queries apart from each other.. do a BEGIN and then 1 and get pg_affected_rows() then do 2 and get pg_affected_rows() and then finally do COMMIT;
Anonymous ¶
19 years ago
That's not quite true, I've been able to execute multiple queries in a single call just fine. In stead, it has to do with the fact this function returns the affected rows for the last executed query, not the last set of queries specified to a single call to pg_query.
Anonymous ¶
19 years ago
Concering Bruno Baguette's note:
The pg_query function only allows one query per function call. When you do your
$sql="BEGIN;
INSERT ...
COMMIT;";
$result=pg_query($conn,$sql);
echo pg_affected_rows($result);
you get a zero, because only the BEGIN; is executed.
The single query per call is, I beleive, a PHP builtin protection against SQL injection attacks. (Ie someone submitting a string paramter that ends the current query and appends another one)
