From f76374f37e8883327eb82d447b3b119360692413 Mon Sep 17 00:00:00 2001
From: Justin Martin <frozenfire@php.net>
Date: Mon, 5 Dec 2011 21:55:40 +0000
Subject: [PATCH] Clarified that certain commands can be used on a result set
 from mysql_unbuffered_query after all rows have been fetched. Closes bug
 #54704.

git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@320465 c90b9560-bf6c-de11-be94-00142212c4b1
---
 reference/mysql/functions/mysql-unbuffered-query.xml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/reference/mysql/functions/mysql-unbuffered-query.xml b/reference/mysql/functions/mysql-unbuffered-query.xml
index 29458775ab..5d344dc8f4 100644
--- a/reference/mysql/functions/mysql-unbuffered-query.xml
+++ b/reference/mysql/functions/mysql-unbuffered-query.xml
@@ -72,9 +72,9 @@
     The benefits of <function>mysql_unbuffered_query</function> come
     at a cost: you cannot use <function>mysql_num_rows</function> and
     <function>mysql_data_seek</function> on a result set returned from
-    <function>mysql_unbuffered_query</function>. You also have to
-    fetch all result rows from an unbuffered SQL query before you
-    can send a new SQL query to MySQL, using the same
+    <function>mysql_unbuffered_query</function>, until all rows are fetched.
+    You also have to fetch all result rows from an unbuffered SQL query
+    before you can send a new SQL query to MySQL, using the same
     <parameter>link_identifier</parameter>.
    </para>
   </note>