sigmasternchen/php-doc-en
1
0
Fork 0
mirror of https://github.com/sigmasternchen/php-doc-en synced 2025-03-16 00:48:54 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Various grammatical fixes.

Browse source 
Addresses bug #49720.


git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@288979 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
Torben Wilson 2009-09-30 06:43:31 +00:00
parent 37cf763bbc
commit 70d7a83993
1 changed files with 16 additions and 15 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

31
reference/mysql/functions/mysql-unbuffered-query.xml
View file

@ -3,7 +3,7 @@
<refentry xml:id="function.mysql-unbuffered-query" xmlns="http://docbook.org/ns/docbook">
<refnamediv>
<refname>mysql_unbuffered_query</refname>
<refpurpose>Send an SQL query to MySQL, without fetching and buffering the result rows</refpurpose>
<refpurpose>Send an SQL query to MySQL without fetching and buffering the result rows.</refpurpose>
</refnamediv>
<refsect1 role="description">
@ -14,17 +14,18 @@
<methodparam choice="opt"><type>resource</type><parameter>link_identifier</parameter></methodparam>
</methodsynopsis>
<para>
<function>mysql_unbuffered_query</function> sends a SQL query
<parameter>query</parameter> to MySQL, without fetching and
buffering the result rows automatically, as
<function>mysql_query</function> 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. When using multiple DB-connects, you
have to specify the optional parameter
<parameter>link_identifier</parameter>.
<function>mysql_unbuffered_query</function> sends the SQL query
<parameter>query</parameter> to MySQL without automatically
fetching and buffering the result rows as
<function>mysql_query</function> does. This saves a considerable
amount of memory with SQL queries that produce large result sets,
and you can start working on the result set immediately after the
first row has been retrieved as you don't have to wait until the
complete SQL query has been performed. To use
<function>mysql_unbuffered_query</function> while multiple database
connections are open, you must specify the optional parameter
<parameter>link_identifier</parameter> to identify which connection
you want to use.
</para>
</refsect1>
@ -36,7 +37,7 @@
<term><parameter>query</parameter></term>
<listitem>
<para>
A SQL query
The SQL query to execute.
</para>
<para>
Data inside the query should be <link
@ -69,10 +70,10 @@
<note>
<para>
The benefits of <function>mysql_unbuffered_query</function> come
at a cost: You cannot use <function>mysql_num_rows</function> and
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
fetch all result rows from an unbuffered SQL query before you
can send a new SQL query to MySQL.
</para>
</note>