From 10b4cb27c5f7d2f564585dde8994bc3631491772 Mon Sep 17 00:00:00 2001
From: Friedhelm Betz <betz@php.net>
Date: Wed, 18 Jun 2003 19:55:19 +0000
Subject: [PATCH] also mention mysql_data_seek (from user notes)

git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@132384 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 ee3c8b41cc..f10695fcf1 100644
--- a/reference/mysql/functions/mysql-unbuffered-query.xml
+++ b/reference/mysql/functions/mysql-unbuffered-query.xml
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.4 $ -->
+<!-- $Revision: 1.5 $ -->
 <!-- splitted from ./en/functions/mysql.xml, last change in rev 1.2 -->
   <refentry id="function.mysql-unbuffered-query">
    <refnamediv>
@@ -32,8 +32,8 @@
     <note>
      <para>
       The benefits of <function>mysql_unbuffered_query</function> come
-      at a cost: You cannot use <function>mysql_num_rows</function> on
-      a result set returned from
+      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.