Author: jstephens
Date: 2008-08-20 20:35:14 +0200 (Wed, 20 Aug 2008)
New Revision: 11583
Log:
"a SQL" -> "an SQL" (Thanks, PeterG!)
Modified:
trunk/cy/query-browser/tour.xml
trunk/dynamic-docs/changelog/connector-odbc.xml
trunk/dynamic-docs/changelog/mysqld-1.xml
trunk/dynamic-docs/changelog/mysqld.xml
trunk/dynamic-docs/changelog/workbench.xml
trunk/mysqldoc-guide/special-markup.xml
trunk/mysqldoc-guide/writing.xml
trunk/mysqltest/command-reference.xml
trunk/mysqltest/introduction.xml
trunk/mysqltest/programs.xml
trunk/query-browser/tour.xml
trunk/refman-4.1/apis-c.xml
trunk/refman-5.0/apis-c.xml
trunk/refman-5.0/programs-client-core.xml
trunk/refman-5.0/se-federated.xml
trunk/refman-5.0/sql-syntax-transactions.xml
trunk/refman-5.1/apis-c.xml
trunk/refman-5.1/dba-core.xml
trunk/refman-5.1/programs-client-core.xml
trunk/refman-5.1/se-federated.xml
trunk/refman-5.1/se-innodb-core.xml
trunk/refman-5.1/sql-syntax-transactions.xml
trunk/refman-6.0/apis-c.xml
trunk/refman-6.0/dba-core.xml
trunk/refman-6.0/programs-client-core.xml
trunk/refman-6.0/se-federated.xml
trunk/refman-6.0/se-innodb-core.xml
trunk/refman-6.0/sql-syntax-transactions.xml
trunk/refman-common/apis-php-mysql.xml
trunk/refman-common/apis-php-mysqli.xml
trunk/refman-common/bug-reports.xml
trunk/refman-common/connector-net.xml
trunk/th/query-browser/tour.xml
trunk/th/refman-common/bug-reports.xml
trunk/th/refman-common/connector-net.xml
trunk/th/refman-common/connector-odbc.xml
Modified: trunk/cy/query-browser/tour.xml
===================================================================
--- trunk/cy/query-browser/tour.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/cy/query-browser/tour.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 575 bytes
@@ -846,7 +846,7 @@
To open a script in the Script Editor, choose the <guimenu>Open
Script ...</guimenu> option from the <guimenu>File</guimenu> menu.
You can also press the <keycap>Ctrl</keycap> + <keycap>O</keycap>
- keys to open a SQL script.
+ keys to open an SQL script.
</para>
<para>
Modified: trunk/dynamic-docs/changelog/connector-odbc.xml
===================================================================
--- trunk/dynamic-docs/changelog/connector-odbc.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/dynamic-docs/changelog/connector-odbc.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 760 bytes
@@ -463,7 +463,7 @@
Accessing a parameer with the type of
<literal>SQL_C_CHAR</literal>, but with a numeric type and a
length of zero, the parameter marker would get stropped from the
- query. In addition, a SQL injection was possible if the
+ query. In addition, an SQL injection was possible if the
parameter value had a non-zero length and was not numeric, the
text would be inserted verbatim.
</para>
Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 912 bytes
@@ -2805,7 +2805,7 @@
<para>
Nested multi-range reads failed when the second multi-range read
released the first read's unprocessed operations, sometimes
- leading to a SQL node crash.
+ leading to an SQL node crash.
</para>
</message>
@@ -23594,7 +23594,7 @@
<para>
<command>mysql_install_db</command> failed if the server was
- running with a SQL mode of <literal>TRADITIONAL</literal>. This
+ running with an SQL mode of <literal>TRADITIONAL</literal>. This
program now resets the SQL mode internally to avoid this
problem.
</para>
Modified: trunk/dynamic-docs/changelog/mysqld.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/dynamic-docs/changelog/mysqld.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1056 bytes
@@ -99248,7 +99248,7 @@
become invalid because a table named in the view definition had
been dropped. Instead, it quit with an error message. Now you
can specify the <option>--force</option> option to cause
- <command>mysqldump</command> to keep going and write a SQL
+ <command>mysqldump</command> to keep going and write an SQL
comment containing the view definition to the dump output.
</para>
@@ -133997,7 +133997,7 @@
<message>
<para>
- Slave servers would retry the execution of a SQL statement an
+ Slave servers would retry the execution of an SQL statement an
infinite number of times, ignoring the value
<literal>SLAVE_TRANSACTION_RETRIES</literal> when using the NDB
engine.
Modified: trunk/dynamic-docs/changelog/workbench.xml
===================================================================
--- trunk/dynamic-docs/changelog/workbench.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/dynamic-docs/changelog/workbench.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 684 bytes
@@ -1134,7 +1134,7 @@
<message>
<para>
- After reverse engineering a SQL create script and drawing some
+ After reverse engineering an SQL create script and drawing some
EER diagrams, a subsequent import of the same script destroys
the EER diagrams. All tables in the catalog are updated, but the
reference of the table in the diagram to the table in the
Modified: trunk/mysqldoc-guide/special-markup.xml
===================================================================
--- trunk/mysqldoc-guide/special-markup.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/mysqldoc-guide/special-markup.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 742 bytes
@@ -834,8 +834,8 @@
The <literal>role</literal> attribute, if present, identifies
the type of function. The value should be
<literal>"capi"</literal> for a C API function,
- <literal>"sql"</literal> for a SQL function, or
- <literal>"sqlop"</literal> for a SQL operator.
+ <literal>"sql"</literal> for an SQL function, or
+ <literal>"sqlop"</literal> for an SQL operator.
</para>
</listitem>
Modified: trunk/mysqldoc-guide/writing.xml
===================================================================
--- trunk/mysqldoc-guide/writing.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/mysqldoc-guide/writing.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 759 bytes
@@ -65,7 +65,7 @@
Within a chapter or other section you define a paragraph of
content using the <literal>para</literal> tag. To define a
fragment of enclosed text so that it appears in mono-spaced font,
- for example when specifying the name of a SQL keyword, command or
+ for example when specifying the name of an SQL keyword, command or
filename, use the <literal>literal</literal>,
<literal>command</literal>, or <literal>filename</literal> tags
accordingly.
Modified: trunk/mysqltest/command-reference.xml
===================================================================
--- trunk/mysqltest/command-reference.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/mysqltest/command-reference.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1145 bytes
@@ -1046,7 +1046,7 @@
Specify one or more comma-separated error values that the next
command is expected to return. Each
<replaceable>error_code</replaceable> value is a
- MySQL-specific error number or a SQLSTATE value. (These are
+ MySQL-specific error number or an SQLSTATE value. (These are
the kinds of values returned by the
<literal>mysql_errno()</literal> and
<literal>mysql_sqlstate()</literal> C API functions,
@@ -1054,7 +1054,7 @@
</para>
<para>
- If you specify a SQLSTATE value, it should begin with an
+ If you specify an SQLSTATE value, it should begin with an
<literal>S</literal> to enable <command>mysqltest</command> to
distinguish it from a MySQL error number. For example, the
error number 1050 and the SQLSTATE value
Modified: trunk/mysqltest/introduction.xml
===================================================================
--- trunk/mysqltest/introduction.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/mysqltest/introduction.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 562 bytes
@@ -131,7 +131,7 @@
<listitem>
<para>
A test case can fail if an error was expected but did not occur
- (for example, if a SQL statement succeeded when it should have
+ (for example, if an SQL statement succeeded when it should have
failed).
</para>
</listitem>
Modified: trunk/mysqltest/programs.xml
===================================================================
--- trunk/mysqltest/programs.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/mysqltest/programs.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 511 bytes
@@ -145,7 +145,7 @@
<listitem>
<para>
- Can test whether the result from a SQL statement or shell
+ Can test whether the result from an SQL statement or shell
command is as expected
</para>
</listitem>
Modified: trunk/query-browser/tour.xml
===================================================================
--- trunk/query-browser/tour.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/query-browser/tour.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 566 bytes
@@ -846,7 +846,7 @@
To open a script in the Script Editor, choose the <guimenu>Open
Script ...</guimenu> option from the <guimenu>File</guimenu> menu.
You can also press the <keycap>Ctrl</keycap> + <keycap>O</keycap>
- keys to open a SQL script.
+ keys to open an SQL script.
</para>
<para>
Modified: trunk/refman-4.1/apis-c.xml
===================================================================
--- trunk/refman-4.1/apis-c.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/refman-4.1/apis-c.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1097 bytes
@@ -9058,7 +9058,7 @@
<listitem>
<para>
- If you fetch a SQL <literal>MEDIUMINT</literal> column value,
+ If you fetch an SQL <literal>MEDIUMINT</literal> column value,
but specify a <literal>buffer_type</literal> value of
<literal>MYSQL_TYPE_LONGLONG</literal> and use a C variable of
type <literal>long long int</literal> as the destination
@@ -12480,7 +12480,7 @@
<para>
It is unnecessary to call
<function role="capi">mysql_stmt_store_result()</function> after
- executing a SQL statement that does not produce a result set,
+ executing an SQL statement that does not produce a result set,
but if you do, it does not harm or cause any notable performance
problem. You can detect whether the statement produced a result
set by checking if
Modified: trunk/refman-5.0/apis-c.xml
===================================================================
--- trunk/refman-5.0/apis-c.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/refman-5.0/apis-c.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1097 bytes
@@ -9294,7 +9294,7 @@
<listitem>
<para>
- If you fetch a SQL <literal>MEDIUMINT</literal> column value,
+ If you fetch an SQL <literal>MEDIUMINT</literal> column value,
but specify a <literal>buffer_type</literal> value of
<literal>MYSQL_TYPE_LONGLONG</literal> and use a C variable of
type <literal>long long int</literal> as the destination
@@ -12650,7 +12650,7 @@
<para>
It is unnecessary to call
<function role="capi">mysql_stmt_store_result()</function> after
- executing a SQL statement that does not produce a result set,
+ executing an SQL statement that does not produce a result set,
but if you do, it does not harm or cause any notable performance
problem. You can detect whether the statement produced a result
set by checking if
Modified: trunk/refman-5.0/programs-client-core.xml
===================================================================
--- trunk/refman-5.0/programs-client-core.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/refman-5.0/programs-client-core.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 750 bytes
@@ -6155,7 +6155,7 @@
<option>--force</option>, <command>mysqldump</command> exits
with an error message. With <option>--force</option>,
<command>mysqldump</command> prints the error message, but
- it also writes a SQL comment containing the view definition
+ it also writes an SQL comment containing the view definition
to the dump output and continues executing.
</para>
</listitem>
Modified: trunk/refman-5.0/se-federated.xml
===================================================================
--- trunk/refman-5.0/se-federated.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/refman-5.0/se-federated.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 627 bytes
@@ -119,7 +119,7 @@
</para>
<para>
- When a client issues a SQL statement that refers to a
+ When a client issues an SQL statement that refers to a
<literal>FEDERATED</literal> table, the flow of information
between the local server (where the SQL statement is executed) and
the remote server (where the data is physically stored) is as
Modified: trunk/refman-5.0/sql-syntax-transactions.xml
===================================================================
--- trunk/refman-5.0/sql-syntax-transactions.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/refman-5.0/sql-syntax-transactions.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 580 bytes
@@ -1237,7 +1237,7 @@
<para>
Currently, among the MySQL Connectors, MySQL Connector/J 5.0.0
supports XA directly (by means of a class interface that handles
- the XA SQL statement interface for you).
+ the Xan SQL statement interface for you).
</para>
<para>
Modified: trunk/refman-5.1/apis-c.xml
===================================================================
--- trunk/refman-5.1/apis-c.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/refman-5.1/apis-c.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1097 bytes
@@ -9389,7 +9389,7 @@
<listitem>
<para>
- If you fetch a SQL <literal>MEDIUMINT</literal> column value,
+ If you fetch an SQL <literal>MEDIUMINT</literal> column value,
but specify a <literal>buffer_type</literal> value of
<literal>MYSQL_TYPE_LONGLONG</literal> and use a C variable of
type <literal>long long int</literal> as the destination
@@ -12749,7 +12749,7 @@
<para>
It is unnecessary to call
<function role="capi">mysql_stmt_store_result()</function> after
- executing a SQL statement that does not produce a result set,
+ executing an SQL statement that does not produce a result set,
but if you do, it does not harm or cause any notable performance
problem. You can detect whether the statement produced a result
set by checking if
Modified: trunk/refman-5.1/dba-core.xml
===================================================================
--- trunk/refman-5.1/dba-core.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/refman-5.1/dba-core.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 659 bytes
@@ -12681,7 +12681,7 @@
<listitem>
<para>
- Log contents are accessible via SQL statements. This enables
+ Log contents are accessible vian SQL statements. This enables
the use of queries that select only those log entries that
satisfy specific criteria. For example, to select log
contents associated with a particular client (which can be
Modified: trunk/refman-5.1/programs-client-core.xml
===================================================================
--- trunk/refman-5.1/programs-client-core.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/refman-5.1/programs-client-core.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 750 bytes
@@ -6401,7 +6401,7 @@
<option>--force</option>, <command>mysqldump</command> exits
with an error message. With <option>--force</option>,
<command>mysqldump</command> prints the error message, but
- it also writes a SQL comment containing the view definition
+ it also writes an SQL comment containing the view definition
to the dump output and continues executing.
</para>
</listitem>
Modified: trunk/refman-5.1/se-federated.xml
===================================================================
--- trunk/refman-5.1/se-federated.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/refman-5.1/se-federated.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 629 bytes
@@ -133,7 +133,7 @@
</figure>
<para>
- When a client issues a SQL statement that refers to a
+ When a client issues an SQL statement that refers to a
<literal>FEDERATED</literal> table, the flow of information
between the local server (where the SQL statement is executed) and
the remote server (where the data is physically stored) is as
Modified: trunk/refman-5.1/se-innodb-core.xml
===================================================================
--- trunk/refman-5.1/se-innodb-core.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/refman-5.1/se-innodb-core.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 716 bytes
@@ -2532,7 +2532,7 @@
<para>
In the case of statement-based replication, this means that
- when a SQL statement is replicated on a slave server, the same
+ when an SQL statement is replicated on a slave server, the same
values are used for the auto-increment column as on the master
server. The result of execution of multiple
<literal>INSERT</literal> statements is deterministic, and the
Modified: trunk/refman-5.1/sql-syntax-transactions.xml
===================================================================
--- trunk/refman-5.1/sql-syntax-transactions.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/refman-5.1/sql-syntax-transactions.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 580 bytes
@@ -1294,7 +1294,7 @@
<para>
Currently, among the MySQL Connectors, MySQL Connector/J 5.0.0
supports XA directly (by means of a class interface that handles
- the XA SQL statement interface for you).
+ the Xan SQL statement interface for you).
</para>
<para>
Modified: trunk/refman-6.0/apis-c.xml
===================================================================
--- trunk/refman-6.0/apis-c.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/refman-6.0/apis-c.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1097 bytes
@@ -9306,7 +9306,7 @@
<listitem>
<para>
- If you fetch a SQL <literal>MEDIUMINT</literal> column value,
+ If you fetch an SQL <literal>MEDIUMINT</literal> column value,
but specify a <literal>buffer_type</literal> value of
<literal>MYSQL_TYPE_LONGLONG</literal> and use a C variable of
type <literal>long long int</literal> as the destination
@@ -12658,7 +12658,7 @@
<para>
It is unnecessary to call
<function role="capi">mysql_stmt_store_result()</function> after
- executing a SQL statement that does not produce a result set,
+ executing an SQL statement that does not produce a result set,
but if you do, it does not harm or cause any notable performance
problem. You can detect whether the statement produced a result
set by checking if
Modified: trunk/refman-6.0/dba-core.xml
===================================================================
--- trunk/refman-6.0/dba-core.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/refman-6.0/dba-core.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 659 bytes
@@ -12554,7 +12554,7 @@
<listitem>
<para>
- Log contents are accessible via SQL statements. This enables
+ Log contents are accessible vian SQL statements. This enables
the use of queries that select only those log entries that
satisfy specific criteria. For example, to select log
contents associated with a particular client (which can be
Modified: trunk/refman-6.0/programs-client-core.xml
===================================================================
--- trunk/refman-6.0/programs-client-core.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/refman-6.0/programs-client-core.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 750 bytes
@@ -6432,7 +6432,7 @@
<option>--force</option>, <command>mysqldump</command> exits
with an error message. With <option>--force</option>,
<command>mysqldump</command> prints the error message, but
- it also writes a SQL comment containing the view definition
+ it also writes an SQL comment containing the view definition
to the dump output and continues executing.
</para>
</listitem>
Modified: trunk/refman-6.0/se-federated.xml
===================================================================
--- trunk/refman-6.0/se-federated.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/refman-6.0/se-federated.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 629 bytes
@@ -117,7 +117,7 @@
</figure>
<para>
- When a client issues a SQL statement that refers to a
+ When a client issues an SQL statement that refers to a
<literal>FEDERATED</literal> table, the flow of information
between the local server (where the SQL statement is executed) and
the remote server (where the data is physically stored) is as
Modified: trunk/refman-6.0/se-innodb-core.xml
===================================================================
--- trunk/refman-6.0/se-innodb-core.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/refman-6.0/se-innodb-core.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 716 bytes
@@ -2437,7 +2437,7 @@
<para>
In the case of statement-based replication, this means that
- when a SQL statement is replicated on a slave server, the same
+ when an SQL statement is replicated on a slave server, the same
values are used for the auto-increment column as on the master
server. The result of execution of multiple
<literal>INSERT</literal> statements is deterministic, and the
Modified: trunk/refman-6.0/sql-syntax-transactions.xml
===================================================================
--- trunk/refman-6.0/sql-syntax-transactions.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/refman-6.0/sql-syntax-transactions.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 580 bytes
@@ -1913,7 +1913,7 @@
<para>
Currently, among the MySQL Connectors, MySQL Connector/J 5.0.0
supports XA directly (by means of a class interface that handles
- the XA SQL statement interface for you).
+ the Xan SQL statement interface for you).
</para>
<para>
Modified: trunk/refman-common/apis-php-mysql.xml
===================================================================
--- trunk/refman-common/apis-php-mysql.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/refman-common/apis-php-mysql.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 10, Lines Added: 10, Lines Deleted: 10; 3975 bytes
@@ -1987,7 +1987,7 @@
<link linkend="apis-php-function.mysql-create-db"><function>mysql_create_db</function></link>
is deprecated. It is preferable to use
<link linkend="apis-php-function.mysql-query"><function>mysql_query</function></link>
- to issue a sql <literal>CREATE DATABASE</literal> statement
+ to issue an sql <literal>CREATE DATABASE</literal> statement
instead.
</para>
@@ -2662,7 +2662,7 @@
Be aware that this function does <emphasis>NOT</emphasis>
switch back to the database you were connected before. In
other words, you can't use this function to
- <emphasis>temporarily</emphasis> run a sql query on another
+ <emphasis>temporarily</emphasis> run an sql query on another
database, you would have to manually switch back. Users are
strongly encouraged to use the
<literal>database.table</literal> syntax in their sql queries
@@ -2736,7 +2736,7 @@
associated with the specified link identifier. This function is
deprecated, it is preferable to use
<link linkend="apis-php-function.mysql-query"><function>mysql_query</function></link>
- to issue a sql <literal>DROP DATABASE</literal> statement
+ to issue an sql <literal>DROP DATABASE</literal> statement
instead.
</para>
@@ -6962,7 +6962,7 @@
<para>
This function is deprecated. It is preferable to use
<link linkend="apis-php-function.mysql-query"><function>mysql_query</function></link>
- to issue a SQL <literal>SHOW COLUMNS FROM table [LIKE
+ to issue an SQL <literal>SHOW COLUMNS FROM table [LIKE
'name']</literal> statement instead.
</para>
@@ -7323,7 +7323,7 @@
<para>
This function is deprecated. It is preferable to use
<link linkend="apis-php-function.mysql-query"><function>mysql_query</function></link>
- to issue a SQL <literal>SHOW TABLES [FROM db_name] [LIKE
+ to issue an SQL <literal>SHOW TABLES [FROM db_name] [LIKE
'pattern']</literal> statement instead.
</para>
@@ -8274,7 +8274,7 @@
<listitem>
<para>
- A SQL query
+ an SQL query
</para>
<para>
@@ -8510,7 +8510,7 @@
</para>
<para>
- Escapes special characters in a string for use in a SQL
+ Escapes special characters in a string for use in an SQL
statement
</para>
</listitem>
@@ -9578,7 +9578,7 @@
<para>
This function deprecated. It is preferable to use
<link linkend="apis-php-function.mysql-query"><function>mysql_query</function></link>
- to issue a SQL <literal>SHOW TABLES [FROM db_name] [LIKE
+ to issue an SQL <literal>SHOW TABLES [FROM db_name] [LIKE
'pattern']</literal> statement instead.
</para>
@@ -9888,7 +9888,7 @@
<para>
<link linkend="apis-php-function.mysql-unbuffered-query"><function>mysql_unbuffered_query</function></link>
- sends a SQL query <parameter>query</parameter> to MySQL, without
+ sends an SQL query <parameter>query</parameter> to MySQL, without
fetching and buffering the result rows automatically, as
<link linkend="apis-php-function.mysql-query"><function>mysql_query</function></link>
does. On the one hand, this saves a considerable amount of
@@ -9914,7 +9914,7 @@
<listitem>
<para>
- A SQL query
+ an SQL query
</para>
</listitem>
</varlistentry>
Modified: trunk/refman-common/apis-php-mysqli.xml
===================================================================
--- trunk/refman-common/apis-php-mysqli.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/refman-common/apis-php-mysqli.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 3, Lines Added: 3, Lines Deleted: 3; 975 bytes
@@ -7092,7 +7092,7 @@
</para>
<para>
- Prepare a SQL statement for execution
+ Prepare an SQL statement for execution
</para>
</listitem>
@@ -8158,7 +8158,7 @@
</para>
<para>
- Escapes special characters in a string for use in a SQL
+ Escapes special characters in a string for use in an SQL
statement, taking into account the current charset of the
connection
</para>
@@ -14389,7 +14389,7 @@
</para>
<para>
- Prepare a SQL statement for execution
+ Prepare an SQL statement for execution
</para>
</listitem>
Modified: trunk/refman-common/bug-reports.xml
===================================================================
--- trunk/refman-common/bug-reports.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/refman-common/bug-reports.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 663 bytes
@@ -83,7 +83,7 @@
<listitem>
<para>
- If you get a parse error for a SQL statement, please check your
+ If you get a parse error for an SQL statement, please check your
syntax closely. If you can't find something wrong with it, it's
extremely likely that your current version of MySQL Server
doesn't support the syntax you are using. If you are using the
Modified: trunk/refman-common/connector-net.xml
===================================================================
--- trunk/refman-common/connector-net.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/refman-common/connector-net.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 18, Lines Added: 18, Lines Deleted: 18; 6556 bytes
@@ -702,7 +702,7 @@
<title>Using <literal>MySqlCommand</literal></title>
<para>
- Represents a SQL statement to execute against a MySQL database.
+ Represents an SQL statement to execute against a MySQL database.
This class cannot be inherited.
</para>
@@ -808,7 +808,7 @@
>ExecuteNonQuery</link>,
and closes the connection. To accomplish this, the
<literal>ExecuteNonQuery</literal> is passed a connection string
- and a query string that is a SQL INSERT statement.
+ and a query string that is an SQL INSERT statement.
</para>
<para>
@@ -1309,7 +1309,7 @@
<title>ExecuteNonQuery</title>
<para>
- Executes a SQL statement against the connection and returns
+ Executes an SQL statement against the connection and returns
the number of rows affected.
</para>
@@ -1336,7 +1336,7 @@
<para>
The following example creates a MySqlCommand and then executes
it using ExecuteNonQuery. The example is passed a string that
- is a SQL statement (such as UPDATE, INSERT, or DELETE) and a
+ is an SQL statement (such as UPDATE, INSERT, or DELETE) and a
string to use to connect to the data source.
</para>
@@ -1474,7 +1474,7 @@
<para>
The following example creates a
<literal>MySqlCommand</literal>, then executes it by passing a
- string that is a SQL <literal>SELECT</literal> statement, and
+ string that is an SQL <literal>SELECT</literal> statement, and
a string to use to connect to the data source.
</para>
@@ -1631,7 +1631,7 @@
The following example creates a
<literal>MySqlCommand</literal> and then executes it using
<literal>ExecuteScalar</literal>. The example is passed a
- string that is a SQL statement that returns an aggregate
+ string that is an SQL statement that returns an aggregate
result, and a string to use to connect to the data source.
</para>
@@ -2152,7 +2152,7 @@
<literal>MySqlConnection</literal>, to select rows from a data
source. The example is passed an initialized
<literal>System.Data.DataSet</literal>, a connection string, a
- query string that is a SQL <literal>SELECT</literal> statement,
+ query string that is an SQL <literal>SELECT</literal> statement,
and a string that is the name of the database table. The example
then creates a <literal>MySqlCommandBuilder</literal>.
</para>
@@ -2629,7 +2629,7 @@
<literal>MySqlCommand.ExecuteNonQuery</literal>, and closes the
connection. To accomplish this, the
<literal>ExecuteNonQuery</literal> is passed a connection string
- and a query string that is a SQL INSERT statement.
+ and a query string that is an SQL INSERT statement.
</para>
<para>
@@ -3428,7 +3428,7 @@
<para>
The <literal>Database</literal> property does not update
- dynamically. If you change the current database using a SQL
+ dynamically. If you change the current database using an SQL
statement, then this property may reflect the wrong value. If
you change the current database using the
<literal>ChangeDatabase</literal> method, this property is
@@ -4330,7 +4330,7 @@
<literal>MySqlCommand.ExecuteNonQuery</literal>, and closes the
connection. To accomplish this, the
<literal>ExecuteNonQuery</literal> is passed a connection string
- and a query string that is a SQL INSERT statement.
+ and a query string that is an SQL INSERT statement.
</para>
<para>
@@ -4488,7 +4488,7 @@
<para>
<emphasis role="bold">Parameters:</emphasis>
- <literal>MySqlCommand</literal> that is a SQL
+ <literal>MySqlCommand</literal> that is an SQL
<literal>SELECT</literal> statement or stored procedure and is
set as the <literal>SelectCommand</literal> property of the
<literal>MySqlDataAdapter</literal>.
@@ -4618,7 +4618,7 @@
<para>
<emphasis role="bold">Parameters:</emphasis> A
- <literal>String</literal> that is a SQL
+ <literal>String</literal> that is an SQL
<literal>SELECT</literal> statement or stored procedure to be
used by the <literal>SelectCommand</literal> property of the
<literal>MySqlDataAdapter</literal>.
@@ -4753,7 +4753,7 @@
<para>
<emphasis role="bold">Parameters:</emphasis> A
- <literal>string</literal> that is a SQL
+ <literal>string</literal> that is an SQL
<literal>SELECT</literal> statement or stored procedure to be
used by the <literal>SelectCommand</literal> property of the
<literal>MySqlDataAdapter</literal>.
@@ -4868,7 +4868,7 @@
<title>DeleteCommand</title>
<para>
- Gets or sets a SQL statement or stored procedure used to
+ Gets or sets an SQL statement or stored procedure used to
delete records from the data set.
</para>
@@ -4968,7 +4968,7 @@
<title>InsertCommand</title>
<para>
- Gets or sets a SQL statement or stored procedure used to
+ Gets or sets an SQL statement or stored procedure used to
insert records into the data set.
</para>
@@ -5079,7 +5079,7 @@
<title>UpdateCommand</title>
<para>
- Gets or sets a SQL statement or stored procedure used to
+ Gets or sets an SQL statement or stored procedure used to
updated records in the data source.
</para>
@@ -5197,7 +5197,7 @@
<title>SelectCommand</title>
<para>
- Gets or sets a SQL statement or stored procedure used to
+ Gets or sets an SQL statement or stored procedure used to
select records in the data source.
</para>
@@ -5922,7 +5922,7 @@
<title>Using <literal>MySqlTransaction</literal></title>
<para>
- Represents a SQL transaction to be made in a MySQL database.
+ Represents an SQL transaction to be made in a MySQL database.
This class cannot be inherited.
</para>
Modified: trunk/th/query-browser/tour.xml
===================================================================
--- trunk/th/query-browser/tour.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/th/query-browser/tour.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 575 bytes
@@ -846,7 +846,7 @@
To open a script in the Script Editor, choose the <guimenu>Open
Script ...</guimenu> option from the <guimenu>File</guimenu> menu.
You can also press the <keycap>Ctrl</keycap> + <keycap>O</keycap>
- keys to open a SQL script.
+ keys to open an SQL script.
</para>
<para>
Modified: trunk/th/refman-common/bug-reports.xml
===================================================================
--- trunk/th/refman-common/bug-reports.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/th/refman-common/bug-reports.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 672 bytes
@@ -83,7 +83,7 @@
<listitem>
<para>
- If you get a parse error for a SQL statement, please check your
+ If you get a parse error for an SQL statement, please check your
syntax closely. If you can't find something wrong with it, it's
extremely likely that your current version of MySQL Server
doesn't support the syntax you are using. If you are using the
Modified: trunk/th/refman-common/connector-net.xml
===================================================================
--- trunk/th/refman-common/connector-net.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/th/refman-common/connector-net.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 18, Lines Added: 18, Lines Deleted: 18; 6565 bytes
@@ -702,7 +702,7 @@
<title>Using <literal>MySqlCommand</literal></title>
<para>
- Represents a SQL statement to execute against a MySQL database.
+ Represents an SQL statement to execute against a MySQL database.
This class cannot be inherited.
</para>
@@ -801,7 +801,7 @@
>ExecuteNonQuery</link>,
and closes the connection. To accomplish this, the
<literal>ExecuteNonQuery</literal> is passed a connection string
- and a query string that is a SQL INSERT statement.
+ and a query string that is an SQL INSERT statement.
</para>
<para>
@@ -1302,7 +1302,7 @@
<title>ExecuteNonQuery</title>
<para>
- Executes a SQL statement against the connection and returns
+ Executes an SQL statement against the connection and returns
the number of rows affected.
</para>
@@ -1329,7 +1329,7 @@
<para>
The following example creates a MySqlCommand and then executes
it using ExecuteNonQuery. The example is passed a string that
- is a SQL statement (such as UPDATE, INSERT, or DELETE) and a
+ is an SQL statement (such as UPDATE, INSERT, or DELETE) and a
string to use to connect to the data source.
</para>
@@ -1467,7 +1467,7 @@
<para>
The following example creates a
<literal>MySqlCommand</literal>, then executes it by passing a
- string that is a SQL <literal>SELECT</literal> statement, and
+ string that is an SQL <literal>SELECT</literal> statement, and
a string to use to connect to the data source.
</para>
@@ -1624,7 +1624,7 @@
The following example creates a
<literal>MySqlCommand</literal> and then executes it using
<literal>ExecuteScalar</literal>. The example is passed a
- string that is a SQL statement that returns an aggregate
+ string that is an SQL statement that returns an aggregate
result, and a string to use to connect to the data source.
</para>
@@ -2145,7 +2145,7 @@
<literal>MySqlConnection</literal>, to select rows from a data
source. The example is passed an initialized
<literal>System.Data.DataSet</literal>, a connection string, a
- query string that is a SQL <literal>SELECT</literal> statement,
+ query string that is an SQL <literal>SELECT</literal> statement,
and a string that is the name of the database table. The example
then creates a <literal>MySqlCommandBuilder</literal>.
</para>
@@ -2622,7 +2622,7 @@
<literal>MySqlCommand.ExecuteNonQuery</literal>, and closes the
connection. To accomplish this, the
<literal>ExecuteNonQuery</literal> is passed a connection string
- and a query string that is a SQL INSERT statement.
+ and a query string that is an SQL INSERT statement.
</para>
<para>
@@ -3404,7 +3404,7 @@
<para>
The <literal>Database</literal> property does not update
- dynamically. If you change the current database using a SQL
+ dynamically. If you change the current database using an SQL
statement, then this property may reflect the wrong value. If
you change the current database using the
<literal>ChangeDatabase</literal> method, this property is
@@ -4306,7 +4306,7 @@
<literal>MySqlCommand.ExecuteNonQuery</literal>, and closes the
connection. To accomplish this, the
<literal>ExecuteNonQuery</literal> is passed a connection string
- and a query string that is a SQL INSERT statement.
+ and a query string that is an SQL INSERT statement.
</para>
<para>
@@ -4464,7 +4464,7 @@
<para>
<emphasis role="bold">Parameters:</emphasis>
- <literal>MySqlCommand</literal> that is a SQL
+ <literal>MySqlCommand</literal> that is an SQL
<literal>SELECT</literal> statement or stored procedure and is
set as the <literal>SelectCommand</literal> property of the
<literal>MySqlDataAdapter</literal>.
@@ -4594,7 +4594,7 @@
<para>
<emphasis role="bold">Parameters:</emphasis> A
- <literal>String</literal> that is a SQL
+ <literal>String</literal> that is an SQL
<literal>SELECT</literal> statement or stored procedure to be
used by the <literal>SelectCommand</literal> property of the
<literal>MySqlDataAdapter</literal>.
@@ -4729,7 +4729,7 @@
<para>
<emphasis role="bold">Parameters:</emphasis> A
- <literal>string</literal> that is a SQL
+ <literal>string</literal> that is an SQL
<literal>SELECT</literal> statement or stored procedure to be
used by the <literal>SelectCommand</literal> property of the
<literal>MySqlDataAdapter</literal>.
@@ -4844,7 +4844,7 @@
<title>DeleteCommand</title>
<para>
- Gets or sets a SQL statement or stored procedure used to
+ Gets or sets an SQL statement or stored procedure used to
delete records from the data set.
</para>
@@ -4944,7 +4944,7 @@
<title>InsertCommand</title>
<para>
- Gets or sets a SQL statement or stored procedure used to
+ Gets or sets an SQL statement or stored procedure used to
insert records into the data set.
</para>
@@ -5055,7 +5055,7 @@
<title>UpdateCommand</title>
<para>
- Gets or sets a SQL statement or stored procedure used to
+ Gets or sets an SQL statement or stored procedure used to
updated records in the data source.
</para>
@@ -5173,7 +5173,7 @@
<title>SelectCommand</title>
<para>
- Gets or sets a SQL statement or stored procedure used to
+ Gets or sets an SQL statement or stored procedure used to
select records in the data source.
</para>
@@ -5898,7 +5898,7 @@
<title>Using <literal>MySqlTransaction</literal></title>
<para>
- Represents a SQL transaction to be made in a MySQL database.
+ Represents an SQL transaction to be made in a MySQL database.
This class cannot be inherited.
</para>
Modified: trunk/th/refman-common/connector-odbc.xml
===================================================================
--- trunk/th/refman-common/connector-odbc.xml 2008-08-20 16:55:43 UTC (rev 11582)
+++ trunk/th/refman-common/connector-odbc.xml 2008-08-20 18:35:14 UTC (rev 11583)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 654 bytes
@@ -4467,7 +4467,7 @@
<row>
<entry>Gupta</entry>
<entry>Team Developer</entry>
- <entry>Previously known as Centura Team Developer; Gupta SQL/Windows</entry>
+ <entry>Previously known as Centura Team Developer; Guptan SQL/Windows</entry>
</row>
<row>
<entry>Gensym</entry>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r11583 - in trunk: cy/query-browser dynamic-docs/changelog mysqldoc-guide mysqltest query-browser refman-4.1 refman-5.0... | jon | 20 Aug |
