Author: paul
Date: 2007-10-01 02:00:00 +0200 (Mon, 01 Oct 2007)
New Revision: 7930
Log:
r25158@frost: paul | 2007-09-30 18:57:49 -0500
Kill a bunch of todos.
Modified:
trunk/mysqltest/renamed-nodes.txt
trunk/refman-4.1/apis-c.xml
trunk/refman-4.1/apis.xml
trunk/refman-4.1/dba-core.xml
trunk/refman-4.1/news-3.23.xml
trunk/refman-4.1/news-4.0.xml
trunk/refman-4.1/news-4.1.xml
trunk/refman-4.1/restrictions.xml
trunk/refman-4.1/se-innodb.xml
trunk/refman-4.1/sql-syntax.xml
trunk/refman-5.0/apis-c.xml
trunk/refman-5.0/apis.xml
trunk/refman-5.0/dba-core.xml
trunk/refman-5.0/news-5.0.xml
trunk/refman-5.0/renamed-nodes.txt
trunk/refman-5.0/restrictions.xml
trunk/refman-5.1/apis-c.xml
trunk/refman-5.1/apis-progutils.xml
trunk/refman-5.1/dba-core.xml
trunk/refman-5.1/news-5.1.xml
trunk/refman-5.1/restrictions.xml
trunk/refman-5.2/apis-c.xml
trunk/refman-5.2/apis-progutils.xml
trunk/refman-5.2/dba-core.xml
trunk/refman-5.2/restrictions.xml
Property changes on: trunk
Name: svk:merge
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:30496
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:25132
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:20005
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:30496
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:25158
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:20005
Modified: trunk/mysqltest/renamed-nodes.txt
trunk/mysqltest/renamed-nodes.txt 2007-09-29 15:03:42 UTC (rev 7929)
+++ trunk/mysqltest/renamed-nodes.txt 2007-10-01 00:00:00 UTC (rev 7930)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 10; 732 bytes
@@ -20,13 +20,3 @@
# comments and ignored.
#
mysql-test-run mysql-test-run-pl
-
-# Test non-expired redirections to local page, external page, URL
-redirect-a mysql-test-run-pl 2008-01-01
-redirect-b ../../refman/4.1/en/charset-map 2008-01-01
-redirect-c
http://dev.mysql.com 2008-01-01
-
-# Test expired redirections to local page, external page, URL
-expired-a mysql-test-run-pl 2007-01-01
-expired-b ../../refman/4.1/en/charset-map 2007-01-01
-expired-c
http://dev.mysql.com 2007-01-01
Modified: trunk/refman-4.1/apis-c.xml
trunk/refman-4.1/apis-c.xml 2007-09-29 15:03:42 UTC (rev 7929)
+++ trunk/refman-4.1/apis-c.xml 2007-10-01 00:00:00 UTC (rev 7930)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 5; 805 bytes
@@ -9079,11 +9079,7 @@
mysql_stmt_prepare()
- Prepares an SQL string for execution.
-
-
- this description is not helpful.
-
+ Prepares an SQL string for execution.
mysql_stmt_reset()
Modified: trunk/refman-4.1/apis.xml
trunk/refman-4.1/apis.xml 2007-09-29 15:03:42 UTC (rev 7929)
+++ trunk/refman-4.1/apis.xml 2007-10-01 00:00:00 UTC (rev 7930)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 4; 491 bytes
@@ -1079,10 +1079,6 @@
<title>MySQL Program Development Utilities</title>
<remark role="todo">
my_print_defaults
</remark>
-
<para>
This section describes some utilities that you may find useful
when developing MySQL programs.
Modified: trunk/refman-4.1/dba-core.xml
trunk/refman-4.1/dba-core.xml 2007-09-29 15:03:42 UTC (rev 7929)
+++ trunk/refman-4.1/dba-core.xml 2007-10-01 00:00:00 UTC (rev 7930)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 593 bytes
@@ -2931,7 +2931,7 @@
</para>
- Kep the Unix description first, because the option name
+ Put the Unix description first because the option name
relates directly to the Unix meaning. Putting the Windows
meaning first makes this more confusing.
Modified: trunk/refman-4.1/news-3.23.xml
trunk/refman-4.1/news-3.23.xml 2007-09-29 15:03:42 UTC (rev 7929)
+++ trunk/refman-4.1/news-3.23.xml 2007-10-01 00:00:00 UTC (rev 7930)
Changed blocks: 2, Lines Added: 0, Lines Deleted: 10; 960 bytes
@@ -76,11 +76,6 @@
<section id="news-3-23-59">
<title>Changes in release 3.23.59 (Not yet released)</title>&eol-warning;
-
- References to bug numbers should be written after the sentence
- describing the bugfix, like this: This sentence describes the fix.
- (Bug #nnnn)
-
@@ -7504,11 +7499,6 @@
-
- delete arguments from these functions, just list in name()
- form?
-
-
The following functions are now multi-byte-safe:
LOCATE(substr ,str ) ,
Modified: trunk/refman-4.1/news-4.0.xml
trunk/refman-4.1/news-4.0.xml 2007-09-29 15:03:42 UTC (rev 7929)
+++ trunk/refman-4.1/news-4.0.xml 2007-10-01 00:00:00 UTC (rev 7930)
Changed blocks: 6, Lines Added: 0, Lines Deleted: 78; 3054 bytes
@@ -186,28 +186,7 @@
&enterprise-offering-note;
<remark role="todo">
Uncomment following when there are feature changes to document for
this release.
</remark>
-
-<!--
<para>
Functionality added or changed:
</para>
-
<itemizedlist>
-
<listitem>
<para>
-
</para>
</listitem>
-
</itemizedlist>
-->
-
<para>
Bugs fixed:
</para>
@@ -239,27 +218,6 @@
&enterprise-offering-note;
<remark role="todo">
Uncomment following when there are feature changes to document for
this release.
</remark>
-
-<!--
<para>
Functionality added or changed:
</para>
-
<itemizedlist>
-
<listitem>
<para>
-
</para>
</listitem>
-
</itemizedlist>
--->
-
<para>
Bugs fixed:
</para>
@@ -406,14 +364,6 @@
<title>Changes in release 4.0.27 (06 May 2006)</title>&eol-warning;
<remark role="note">
References to bug numbers should be written after the sentence
describing the bugfix, like this: This sentence describes the fix.
(Bug #nnnn) It is not necessary to state that the bug was fixed,
since "Bugs fixed" already implies this. Use the past tense in
describing the bug.
</remark>
-
<para>
This is a security fix release and bugfix release for the MySQL
4.0 release family.
@@ -665,14 +615,6 @@
<title>Changes in release 4.0.26 (08 September 2005)</title>&eol-warning;
<remark role="note">
References to bug numbers should be written after the sentence
describing the bugfix, like this: This sentence describes the fix.
(Bug #nnnn) It is not necessary to state that the bug was fixed,
since "Bugs fixed" already implies this. Use the past tense in
describing the bug.
</remark>
-
<para>
Functionality added or changed:
</para>
@@ -766,14 +708,6 @@
<title>Changes in release 4.0.25 (05 July 2005)</title>&eol-warning;
<remark role="note">
References to bug numbers should be written after the sentence
describing the bugfix, like this: This sentence describes the fix.
(Bug #nnnn) It is not necessary to state that the bug was fixed,
since "Bugs fixed" already implies this. Use the past tense in
describing the bug.
</remark>
-
<para>
Functionality added or changed:
</para>
@@ -1908,18 +1842,6 @@
<title>Changes in release 4.0.21 (06 September 2004)</title>&eol-warning;
<remark role="note">
References to bug numbers should be written after the sentence
</remark>
-
<remark role="note">
describing the bugfix, like this:
</remark>
-
<remark role="note">
This sentence describes the fix. (Bug #nnnn)
</remark>
-
<para>
Functionality added or changed:
</para>
Modified: trunk/refman-4.1/news-4.1.xml
trunk/refman-4.1/news-4.1.xml 2007-09-29 15:03:42 UTC (rev 7929)
+++ trunk/refman-4.1/news-4.1.xml 2007-10-01 00:00:00 UTC (rev 7930)
Changed blocks: 8, Lines Added: 0, Lines Deleted: 44; 2689 bytes
@@ -4714,12 +4714,6 @@
<title>Changes in release 4.1.16 (29 November 2005)</title>&eol-warning;
<remark role="note">
References to bug numbers should be written after the sentence
describing the bugfix, like this: This sentence describes the fix.
(Bug #nnnn)
</remark>
-
<para>
Functionality added or changed:
</para>
@@ -4806,11 +4800,6 @@
Bugs fixed:
-
- No need to start every item with "Fixed..."; sufficient to
- describe the issue that was fixed. Use past tense.
- </remark>
-
<itemizedlist>
<listitem>
@@ -5308,12 +5297,6 @@
<title>Changes in release 4.1.15 (13 October 2005)</title>&eol-warning;
<remark role="note">
References to bug numbers should be written after the sentence
describing the bugfix, like this: This sentence describes the fix.
(Bug #nnnn)
</remark>
-
<para>
Functionality added or changed:
</para>
@@ -5382,11 +5365,6 @@
Bugs fixed:
-
- No need to start every item with "Fixed..."; sufficient to
- describe the issue that was fixed. Use past tense.
- </remark>
-
<itemizedlist>
<listitem>
@@ -6041,12 +6019,6 @@
<title>Changes in release 4.1.14 (17 August 2005)</title>&eol-warning;
<remark role="note">
References to bug numbers should be written after the sentence
describing the bugfix, like this: This sentence describes the fix.
(Bug #nnnn)
</remark>
-
<para>
Functionality added or changed:
</para>
@@ -6120,11 +6092,6 @@
Bugs fixed:
-
- No need to start every item with "Fixed..."; sufficient to
- describe the issue that was fixed. Use past tense.
- </remark>
-
<itemizedlist>
<listitem>
@@ -6591,12 +6558,6 @@
<title>Changes in release 4.1.13 (15 July 2005)</title>&eol-warning;
<remark role="note">
References to bug numbers should be written after the sentence
describing the bugfix, like this: This sentence describes the fix.
(Bug #nnnn)
</remark>
-
<para>
Functionality added or changed:
</para>
@@ -6757,11 +6718,6 @@
Bugs fixed:
-
- No need to start every item with "Fixed..."; sufficient to
- describe the issue that was fixed. Use past tense.
- </remark>
-
<itemizedlist>
<remark>
Modified: trunk/refman-4.1/restrictions.xml
trunk/refman-4.1/restrictions.xml 2007-09-29 15:03:42 UTC (rev 7929)
+++ trunk/refman-4.1/restrictions.xml 2007-10-01 00:00:00 UTC (rev 7930)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 4; 552 bytes
@@ -435,10 +435,6 @@
<title>The Maximum Number of Columns Per Table</title>
<remark role="todo">
There are still some questions to be resolved here.
</remark>
-
<indexterm>
<primary>maximums</primary>
<secondary>maximum columns per table</secondary>
Modified: trunk/refman-4.1/se-innodb.xml
trunk/refman-4.1/se-innodb.xml 2007-09-29 15:03:42 UTC (rev 7929)
+++ trunk/refman-4.1/se-innodb.xml 2007-10-01 00:00:00 UTC (rev 7930)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 4; 503 bytes
@@ -1678,10 +1678,6 @@
</listitem>
-
- document innodb_sync_spin_loops
-
-
innodb_safe_binlog
Modified: trunk/refman-4.1/sql-syntax.xml
trunk/refman-4.1/sql-syntax.xml 2007-09-29 15:03:42 UTC (rev 7929)
+++ trunk/refman-4.1/sql-syntax.xml 2007-10-01 00:00:00 UTC (rev 7930)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 550 bytes
@@ -16374,7 +16374,7 @@
SHOW OPEN TABLES
-
+
SHOW OPEN TABLES grammar allows FROM and LIKE clauses, but
they do not appear to work, so they're not listed here.
Modified: trunk/refman-5.0/apis-c.xml
trunk/refman-5.0/apis-c.xml 2007-09-29 15:03:42 UTC (rev 7929)
+++ trunk/refman-5.0/apis-c.xml 2007-10-01 00:00:00 UTC (rev 7930)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 5; 725 bytes
@@ -9276,11 +9276,7 @@
mysql_stmt_prepare()
- Prepares an SQL string for execution.
-
-
- This description is NOT helpful.
-
+ Prepares an SQL string for execution.
Modified: trunk/refman-5.0/apis.xml
trunk/refman-5.0/apis.xml 2007-09-29 15:03:42 UTC (rev 7929)
+++ trunk/refman-5.0/apis.xml 2007-10-01 00:00:00 UTC (rev 7930)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 4; 489 bytes
@@ -609,10 +609,6 @@
<title>MySQL Program Development Utilities</title>
<remark role="todo">
my_print_defaults
</remark>
-
<para>
This section describes some utilities that you may find useful
when developing MySQL programs.
Modified: trunk/refman-5.0/dba-core.xml
trunk/refman-5.0/dba-core.xml 2007-09-29 15:03:42 UTC (rev 7929)
+++ trunk/refman-5.0/dba-core.xml 2007-10-01 00:00:00 UTC (rev 7930)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 700 bytes
@@ -2966,8 +2966,8 @@
--socket=path
-
- Put the Unix description first, because the option name
+
+ The Unix description comes first because the option name
relates directly to the Unix meaning. Putting the Windows
meaning first makes this more confusing.
Modified: trunk/refman-5.0/news-5.0.xml
trunk/refman-5.0/news-5.0.xml 2007-09-29 15:03:42 UTC (rev 7929)
+++ trunk/refman-5.0/news-5.0.xml 2007-10-01 00:00:00 UTC (rev 7930)
Changed blocks: 5, Lines Added: 0, Lines Deleted: 49; 2722 bytes
@@ -9760,14 +9760,6 @@
<title>Changes in release 5.0.14 (Not released)</title>
<remark role="note">
References to bug numbers should be written after the sentence
describing the bugfix, like this: This sentence describes the fix.
(Bug #nnnn) It is not necessary to state that the bug was fixed,
since "Bugs fixed" already implies this. Use the past tense in
describing the bug.
</remark>
-
<para>
Functionality added or changed:
</para>
@@ -13255,12 +13247,6 @@
<title>Changes in release 5.0.8 (Not released)</title>
<remark role="note">
References to bug numbers should be written after the sentence
describing the bugfix, like this: This sentence describes the fix.
(Bug #nnnn)
</remark>
-
<note>
<para>
Starting with version 5.0.8, changes for MySQL Cluster can be
@@ -13400,27 +13386,6 @@
<itemizedlist>
<remark role="note">
No need to start every item with "Fixed..."; sufficient to
describe the issue that was fixed. Use past tense.
</remark>
-
<remark role="todo">
Uncomment the following item when pushed to the 5.0 tree; move
to 5.0.9 bugfixes if necessary.
</remark>
-
-<!--
<listitem>
<para>Queries of the form <literal>UPDATE ... (SELECT ... ) SET
...</literal> run on a replication master would crash all the
slaves.
(<ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2004-4380 ">CVE-2004-4380</ulink>,
Bug #10442)
</para>
</listitem>
--->
-
<remark>
Leave the security fix item as first in the list so it stands
out better
@@ -13986,14 +13951,6 @@
<title>Changes in release 5.0.7 (10 June 2005)</title>
<remark role="note">
References to bug numbers should be written after the sentence
describing the bugfix, like this: This sentence describes the fix.
(Bug #nnnn) It is not necessary to state that the bug was fixed,
since "Bugs fixed" already implies this. Use the past tense in
describing the bug.
</remark>
-
<para>
Functionality added or changed:
</para>
@@ -16160,12 +16117,6 @@
-
- References to bug numbers should be written after the sentence
- describing the bugfix, like this: This sentence describes the fix.
- (Bug #nnnn)
- </remark>
-
Functionality added or changed:
Modified: trunk/refman-5.0/renamed-nodes.txt
trunk/refman-5.0/renamed-nodes.txt 2007-09-29 15:03:42 UTC (rev 7929)
+++ trunk/refman-5.0/renamed-nodes.txt 2007-10-01 00:00:00 UTC (rev 7930)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 10; 783 bytes
@@ -635,13 +635,3 @@
without-dsn myodbc-configuration-connection-without-dsn
write-conflict myodbc-usagenotes-apptips
year-2000-compliance y2k-issues
-
-# Test non-expired redirections to local page, external page, URL
-redirect-a introduction 2008-01-01
-redirect-b ../../4.1/en/charset-map 2008-01-01
-redirect-c
http://dev.mysql.com 2008-01-01
-
-# Test expired redirections to local page, external page, URL
-expired-a introduction 2007-01-01
-expired-b ../../4.1/en/charset-map 2007-01-01
-expired-c
http://dev.mysql.com 2007-01-01
Modified: trunk/refman-5.0/restrictions.xml
trunk/refman-5.0/restrictions.xml 2007-09-29 15:03:42 UTC (rev 7929)
+++ trunk/refman-5.0/restrictions.xml 2007-10-01 00:00:00 UTC (rev 7930)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 4; 554 bytes
@@ -1124,10 +1124,6 @@
<title>The Maximum Number of Columns Per Table</title>
<remark role="todo">
There are still some questions to be resolved here.
</remark>
-
<indexterm>
<primary>maximums</primary>
<secondary>maximum columns per table</secondary>
Modified: trunk/refman-5.1/apis-c.xml
trunk/refman-5.1/apis-c.xml 2007-09-29 15:03:42 UTC (rev 7929)
+++ trunk/refman-5.1/apis-c.xml 2007-10-01 00:00:00 UTC (rev 7930)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 5; 805 bytes
@@ -9342,11 +9342,7 @@
mysql_stmt_prepare()
- Prepares an SQL string for execution.
-
-
- This description is NOT helpful.
-
+ Prepares an SQL string for execution.
mysql_stmt_reset()
Modified: trunk/refman-5.1/apis-progutils.xml
trunk/refman-5.1/apis-progutils.xml 2007-09-29 15:03:42 UTC (rev 7929)
+++ trunk/refman-5.1/apis-progutils.xml 2007-10-01 00:00:00 UTC (rev 7930)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 4; 501 bytes
@@ -9,10 +9,6 @@
<title>MySQL Program Development Utilities</title>
<remark role="todo">
my_print_defaults
</remark>
-
<para>
This section describes some utilities that you may find useful when
developing MySQL programs.
Modified: trunk/refman-5.1/dba-core.xml
trunk/refman-5.1/dba-core.xml 2007-09-29 15:03:42 UTC (rev 7929)
+++ trunk/refman-5.1/dba-core.xml 2007-10-01 00:00:00 UTC (rev 7930)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 686 bytes
@@ -3094,8 +3094,8 @@
<para condition="dynamic:optvar:item" role="5.1:mysqld:socket"/>
<remark role="todo">
Put the Unix description first, because the option name
+ <remark>
+ The Unix description comes first because the option name
relates directly to the Unix meaning. Putting the Windows
meaning first makes this more confusing.
</remark>
Modified: trunk/refman-5.1/news-5.1.xml
trunk/refman-5.1/news-5.1.xml 2007-09-29 15:03:42 UTC (rev 7929)
+++ trunk/refman-5.1/news-5.1.xml 2007-10-01 00:00:00 UTC (rev 7930)
Changed blocks: 7, Lines Added: 0, Lines Deleted: 56; 3699 bytes
@@ -26334,14 +26334,6 @@
<title>Changes in release 5.1.7 (27 February 2006)</title>
<remark role="note">
References to bug numbers should be written after the sentence
describing the bugfix, like this: This sentence describes the fix.
(Bug #nnnn) It is not necessary to state that the bug was fixed,
since "Bugs fixed" already implies this. Use the past tense in
describing the bug.
</remark>
-
<para>
Functionality added or changed:
</para>
@@ -27124,14 +27116,6 @@
<title>Changes in release 5.1.6 (01 February 2006)</title>
<remark role="note">
References to bug numbers should be written after the sentence
describing the bugfix, like this: This sentence describes the fix.
(Bug #nnnn) It is not necessary to state that the bug was fixed,
since "Bugs fixed" already implies this. Use the past tense in
describing the bug.
</remark>
-
<para>
Functionality added or changed:
</para>
@@ -27872,14 +27856,6 @@
<title>Changes in release 5.1.5 (10 January 2006)</title>
<remark role="note">
References to bug numbers should be written after the sentence
describing the bugfix, like this: This sentence describes the fix.
(Bug #nnnn) It is not necessary to state that the bug was fixed,
since "Bugs fixed" already implies this. Use the past tense in
describing the bug.
</remark>
-
<para>
Functionality added or changed:
</para>
@@ -28071,14 +28047,6 @@
<title>Changes in release 5.1.4 (21 December 2005)</title>
<remark role="note">
References to bug numbers should be written after the sentence
describing the bugfix, like this: This sentence describes the fix.
(Bug #nnnn) It is not necessary to state that the bug was fixed,
since "Bugs fixed" already implies this. Use the past tense in
describing the bug.
</remark>
-
<para>
Functionality added or changed:
</para>
@@ -28381,14 +28349,6 @@
<title>Changes in release 5.1.3 (29 November 2005)</title>
<remark role="note">
References to bug numbers should be written after the sentence
describing the bugfix, like this: This sentence describes the fix.
(Bug #nnnn) It is not necessary to state that the bug was fixed,
since "Bugs fixed" already implies this. Use the past tense in
describing the bug.
</remark>
-
<para>
Functionality added or changed:
</para>
@@ -28581,14 +28541,6 @@
<title>Changes in release 5.1.2 (Not released)</title>
<remark role="note">
References to bug numbers should be written after the sentence
describing the bugfix, like this: This sentence describes the fix.
(Bug #nnnn) It is not necessary to state that the bug was fixed,
since "Bugs fixed" already implies this. Use the past tense in
describing the bug.
</remark>
-
<para>
Functionality added or changed:
</para>
@@ -28655,14 +28607,6 @@
<title>Changes in release 5.1.1 (Not released)</title>
<remark role="note">
References to bug numbers should be written after the sentence
describing the bugfix, like this: This sentence describes the fix.
(Bug #nnnn) It is not necessary to state that the bug was fixed,
since "Bugs fixed" already implies this. Use the past tense in
describing the bug.
</remark>
-
<para>
Bugs fixed:
</para>
Modified: trunk/refman-5.1/restrictions.xml
trunk/refman-5.1/restrictions.xml 2007-09-29 15:03:42 UTC (rev 7929)
+++ trunk/refman-5.1/restrictions.xml 2007-10-01 00:00:00 UTC (rev 7930)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 4; 554 bytes
@@ -1161,10 +1161,6 @@
<title>The Maximum Number of Columns Per Table</title>
<remark role="todo">
There are still some questions to be resolved here.
</remark>
-
<indexterm>
<primary>maximums</primary>
<secondary>maximum columns per table</secondary>
Modified: trunk/refman-5.2/apis-c.xml
trunk/refman-5.2/apis-c.xml 2007-09-29 15:03:42 UTC (rev 7929)
+++ trunk/refman-5.2/apis-c.xml 2007-10-01 00:00:00 UTC (rev 7930)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 5; 805 bytes
@@ -9280,11 +9280,7 @@
mysql_stmt_prepare()
- Prepares an SQL string for execution.
-
-
- This description is NOT helpful.
-
+ Prepares an SQL string for execution.
mysql_stmt_reset()
Modified: trunk/refman-5.2/apis-progutils.xml
trunk/refman-5.2/apis-progutils.xml 2007-09-29 15:03:42 UTC (rev 7929)
+++ trunk/refman-5.2/apis-progutils.xml 2007-10-01 00:00:00 UTC (rev 7930)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 4; 501 bytes
@@ -9,10 +9,6 @@
<title>MySQL Program Development Utilities</title>
<remark role="todo">
my_print_defaults
</remark>
-
<para>
This section describes some utilities that you may find useful when
developing MySQL programs.
Modified: trunk/refman-5.2/dba-core.xml
trunk/refman-5.2/dba-core.xml 2007-09-29 15:03:42 UTC (rev 7929)
+++ trunk/refman-5.2/dba-core.xml 2007-10-01 00:00:00 UTC (rev 7930)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 686 bytes
@@ -3038,8 +3038,8 @@
<para condition="dynamic:optvar:item" role="5.2:mysqld:socket"/>
<remark role="todo">
Put the Unix description first, because the option name
+ <remark>
+ The Unix description comes first because the option name
relates directly to the Unix meaning. Putting the Windows
meaning first makes this more confusing.
</remark>
Modified: trunk/refman-5.2/restrictions.xml
trunk/refman-5.2/restrictions.xml 2007-09-29 15:03:42 UTC (rev 7929)
+++ trunk/refman-5.2/restrictions.xml 2007-10-01 00:00:00 UTC (rev 7930)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 4; 554 bytes
@@ -1155,10 +1155,6 @@
<title>The Maximum Number of Columns Per Table</title>
<remark role="todo">
There are still some questions to be resolved here.
</remark>
-
<indexterm>
<primary>maximums</primary>
<secondary>maximum columns per table</secondary>
--
MySQL Code Commits Mailing List
For list archives:
http://lists.mysql.com/commits
To unsubscribe:
http://lists.mysql.com/commits?unsub=lists@pantek.com
Received on Sun Sep 30 20:00:36 2007