From 83a3aa848e7923116d0e09b9bd4c200bbff256ab Mon Sep 17 00:00:00 2001 From: Georg Richter Date: Thu, 30 Aug 2001 20:36:21 +0000 Subject: [PATCH] Bug: 12823 - Changed mysql_unbuffered_query description killed 3rd parameter, mysql_unbuffered_query only accepts 2 parms inserted description for 2nd parameter git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@56327 c90b9560-bf6c-de11-be94-00142212c4b1 --- functions/mysql.xml | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/functions/mysql.xml b/functions/mysql.xml index a7d7c0b4ff..bcf0fac46c 100644 --- a/functions/mysql.xml +++ b/functions/mysql.xml @@ -1,5 +1,5 @@ - + MySQL functions MySQL @@ -1834,7 +1834,7 @@ $result = mysql_query ("SELECT my_col FROM my_tbl") See also: mysql_affected_rows, mysql_db_query, mysql_unbuffered_query, - mysql_free_result, + mysql_free_result/function>, mysql_result, mysql_select_db, and mysql_connect. @@ -1856,13 +1856,10 @@ $result = mysql_query ("SELECT my_col FROM my_tbl") resource link_identifier - int - result_mode - - + - mysql_unbuffered_query sends a SQL query to MySQL, + mysql_unbuffered_query sends a SQL query query to MySQL, without fetching and buffering the result rows automatically, as mysql_query does. On the one hand, this saves a considerable amount of memory with SQL @@ -1870,6 +1867,7 @@ $result = mysql_query ("SELECT my_col FROM my_tbl") working on the result set immediately after the first row has been retrieved: you don't have to wait until the complete SQL query has been performed. + When using multiple DB-connects, you have to specify the optional parameter link_identifier.