[edit] Last updated: Fri, 23 Mar 2012

pg_affected_rows

(PHP 4 >= 4.2.0, PHP 5)

pg_affected_rows — Zwraca liczbę zmodyfikowanych wierszy

Opis

int pg_affected_rows ( resource $result )

pg_affected_rows() zwraca liczbę wierszy dodanych, zmodyfikowanych lub usuniętych przez zapytania INSERT, UPDATE i DELETE.

Informacja:
Ta funkcja była nazwana pg_cmdtuples().

Parametry

result: Zasób, wynik zapytania PostgreSQL, zwrócony przez pg_query(), pg_query_params() lub pg_execute() (wśród innych).

Zwracane wartości

Liczba wierszy na które wpływ ma zapytanie. Jeśli nie wystąpił taki wiersz, zostanie zwrócone 0.

Przykłady

Przykład #1 pg_affected_rows() przykład


<?php
     $result = pg_query($conn, "INSERT INTO authors VALUES ('Orwell', 2002, 'Animal Farm')");
     $cmdtuples = pg_affected_rows ($result);
     echo $cmdtuples . " wiersz(e), na które miało wpływ zapytanie.\n";
?>

Powyższy przykład wyświetli:

1 wiersz(e), na które miało wpływ zapytanie.

Zobacz też:

pg_query() - Realizujezapytanie do bazy danych
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() - Sends a request to execute a prepared statement with given parameters, and waits for the result.
pg_num_rows() - Zwraca liczbę wierszy

pg_cancel_query

Funkcje PostgreSQL

[edit] Last updated: Fri, 23 Mar 2012

add a note User Contributed Notes pg_affected_rows

Anonymous 20-Dec-2007 05:02


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 14-Nov-2007 09:45


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.

05-Aug-2005 06:31


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.

29-Jun-2005 09:15


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)

Bruno Baguette 28-Jun-2005 04:45


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

add a note