diff --git a/functions/mysql.xml b/functions/mysql.xml index 12d2c4d5cd..213352e89b 100644 --- a/functions/mysql.xml +++ b/functions/mysql.xml @@ -479,7 +479,8 @@ while ($i < $cnt) { arguments - See also mysql_connect. + See also mysql_connect and + mysql_query. For downwards @@ -1764,6 +1765,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_result, mysql_select_db, and @@ -1772,6 +1774,50 @@ $result = mysql_query ("SELECT my_col FROM my_tbl") + + + mysql_unbuffered_query + Send an SQL query to MySQL, without fetching and buffering the result rows + + + Description + + + int mysql_unbuffered_query + string query + int + link_identifier + + int + result_mode + + + + + mysql_unbuffered_query sends a SQL 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 + queries that produce large result sets. On the other hand, you can start + 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. + + + + The benefits of mysql_unbuffered_query come at a + cost: You cannot use mysql_num_rows on a result set + returned from mysql_unbuffered_query. You also have + to fetch all result rows from an unbuffered SQL query, before you can + send a new SQL query to MySQL. + + + + See also: mysql_query. + + + + mysql_result