Author: paul
Date: 2007-11-29 19:54:59 +0100 (Thu, 29 Nov 2007)
New Revision: 8995
Log:
r33585@arctic: paul | 2007-11-29 12:53:14 -0600
Fix changelog markup.
Modified:
trunk/dynamic-docs/changelog/mysqld.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:33573
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:27548
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:22282
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:33585
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:27548
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:22282
Modified: trunk/dynamic-docs/changelog/mysqld.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld.xml 2007-11-29 18:10:16 UTC (rev 8994)
+++ trunk/dynamic-docs/changelog/mysqld.xml 2007-11-29 18:54:59 UTC (rev 8995)
Changed blocks: 43, Lines Added: 33, Lines Deleted: 31; 12487 bytes
@@ -6853,6 +6853,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="incompatiblechange"/>
<manual type="CHAR"/>
<manual type="character sets"/>
</tags>
@@ -6864,7 +6865,6 @@
<message>
<para>
- <emphasis role="bold">Warning: Incompatible change.</emphasis>
The <function role="sql">CHAR()</function> function now returns
a binary string rather than a string in the connection character
set. An optional <literal>USING
@@ -8410,6 +8410,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="incompatiblechange"/>
<manual type="CEILING"/>
<manual type="REAL_RESULT"/>
<manual type="NUMERIC"/>
@@ -8433,8 +8434,7 @@
</para>
<para>
- <emphasis role="bold">Warning: Incompatible change:</emphasis> A
- consequence of the change in handling of the
+ A consequence of the change in handling of the
<literal>DECIMAL</literal> and <literal>NUMERIC</literal>
fixed-point data types is that the server is more strict to
follow standard SQL. For example, a data type of
@@ -8452,7 +8452,6 @@
</programlisting>
<para>
- <emphasis role="bold">Warning: Incompatible change:</emphasis>
For user-defined functions, exact-value decimal arguments such
as <literal>1.3</literal> or <literal>DECIMAL</literal> column
values were passed as <literal>REAL_RESULT</literal> values
@@ -9379,6 +9378,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="incompatiblechange"/>
<manual type="mysql_stmt_prepare()"/>
<manual type="mysql_stmt_init()"/>
<manual type="MYSQL_STMT"/>
@@ -9391,7 +9391,6 @@
<message>
<para>
- <emphasis role="bold">Warning: Incompatible change:</emphasis>
The signature of the
<function role="capi">mysql_stmt_prepare()</function> function
was changed to <literal>int mysql_stmt_prepare(MYSQL_STMT *stmt,
@@ -12838,6 +12837,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="incompatiblechange"/>
<manual type="DATETIME"/>
<manual type="YYYYMMDDHHMMSS"/>
</tags>
@@ -12854,7 +12854,6 @@
<message>
<para>
- <emphasis role="bold">Warning: Incompatible change:</emphasis>
Previously, conversion of <literal>DATETIME</literal> values to
numeric form by adding zero produced a result in
<literal>YYYYMMDDHHMMSS</literal> format. The result of
@@ -19053,6 +19052,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="incompatiblechange"/>
<manual type="mysql_bind_param()"/>
<manual type="mysql_bind_result()"/>
<manual type="mysql_execute()"/>
@@ -19083,7 +19083,6 @@
<message>
<para>
- <emphasis role="bold">Warning: Incompatible change:</emphasis>
Renamed prepared statements C API functions:
</para>
@@ -32648,6 +32647,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="incompatiblechange"/>
<manual type="InnoDB"/>
<manual type="transactions"/>
</tags>
@@ -32663,10 +32663,9 @@
<message>
<para>
- <emphasis role="bold">Incompatible change:</emphasis> A lock
- wait timeout caused <literal>InnoDB</literal> to roll back the
- entire current transaction. Now it rolls back only the most
- recent SQL statement.
+ A lock wait timeout caused <literal>InnoDB</literal> to roll
+ back the entire current transaction. Now it rolls back only the
+ most recent SQL statement.
</para>
</message>
@@ -32676,6 +32675,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="incompatiblechange"/>
<manual type="CURRENT_TIMESTAMP"/>
<manual type="TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP"/>
<manual type="UPDATE"/>
@@ -32712,7 +32712,9 @@
be treated as a <literal>TIMESTAMP DEFAULT 0</literal> column.
<literal>NOW</literal> is supported as an alias for
<literal>CURRENT_TIMESTAMP</literal>.
- <emphasis role="bold">Warning: Incompatible change:</emphasis>
+ </para>
+
+ <para>
Unlike in previous versions, explicit specification of default
values for <literal>TIMESTAMP</literal> column is never ignored
and turns off the auto-set feature (unless you have
@@ -33409,6 +33411,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="incompatiblechange"/>
<manual type="SHOW GLOBAL STATUS"/>
<manual type="SHOW STATUS"/>
</tags>
@@ -33420,7 +33423,6 @@
<message>
<para>
- <emphasis role="bold">Warning: Incompatible change!</emphasis>
<literal>SHOW STATUS</literal> now shows the session
(thread-specific) status variables and <literal>SHOW GLOBAL
STATUS</literal> shows the status variables for the whole
@@ -51848,6 +51850,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="incompatiblechange"/>
<manual type="DROP TRIGGER"/>
<manual type="triggers"/>
</tags>
@@ -51863,10 +51866,9 @@
<message>
<para>
- <emphasis role="bold">Incompatible change:</emphasis> The
- namespace for triggers has changed. Previously, trigger names
- had to be unique per table. Now they must be unique within the
- schema (database). An implication of this change is that
+ The namespace for triggers has changed. Previously, trigger
+ names had to be unique per table. Now they must be unique within
+ the schema (database). An implication of this change is that
<literal>DROP TRIGGER</literal> syntax now uses a schema name
instead of a table name (schema name is optional and, if
omitted, the current schema will be used).
@@ -60547,6 +60549,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="incompatiblechange"/>
<manual type="mysql_get_metadata()"/>
<manual type="mysql_prepare_result()"/>
</tags>
@@ -60558,7 +60561,6 @@
<message>
<para>
- <emphasis role="bold">Warning: Incompatible change:</emphasis>
Renamed the C API <function>mysql_prepare_result()</function>
function to <function>mysql_get_metadata()</function> because
the old name was confusing.
@@ -64961,6 +64963,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="incompatiblechange"/>
<manual type="BINARY"/>
</tags>
@@ -64971,7 +64974,6 @@
<message>
<para>
- <emphasis role="bold">Warning: Incompatible change.</emphasis>
For <literal>BINARY</literal> columns, the pad value and how it
is handled has changed. The pad value for inserts now is
<literal>0x00</literal> rather than space, and there is no
@@ -70049,6 +70051,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="incompatiblechange"/>
<manual type="timezone"/>
<manual type="system_time_zone"/>
</tags>
@@ -70060,7 +70063,6 @@
<message>
<para>
- <emphasis role="bold">Warning: Incompatible change:</emphasis>
The <literal>timezone</literal> system variable has been removed
and replaced by <literal>system_time_zone</literal>. See
<xref linkend="server-system-variables"/>.
@@ -73756,6 +73758,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="incompatiblechange"/>
<manual type="CHECK TABLES"/>
<manual type="VARCHAR"/>
<manual type="CHAR"/>
@@ -73772,7 +73775,6 @@
<message>
<para>
- <emphasis role="bold">Warning: Incompatible change:</emphasis>
String comparison now works according to the SQL standard.
Because we have that <literal>'a' = 'a '</literal> then from it
must follow that <literal>'a' > 'a\t'</literal>. (The latter
@@ -75525,6 +75527,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="incompatiblechange"/>
<manual type="mysql_shutdown()"/>
</tags>
@@ -75536,8 +75539,7 @@
<message>
<para>
- <emphasis role="bold">Warning: Incompatible change:</emphasis> C
- API change: <function role="capi">mysql_shutdown()</function>
+ C API change: <function role="capi">mysql_shutdown()</function>
now requires a second argument. This is a source-level
incompatibility that affects how you compile client programs; it
does not affect the ability of compiled clients to communicate
@@ -84055,6 +84057,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="incompatiblechange"/>
<manual type="TIMESTAMP"/>
</tags>
@@ -84065,7 +84068,6 @@
<message>
<para>
- <emphasis role="bold">Warning: Incompatible change:</emphasis>
<literal>TIMESTAMP</literal> is now returned as a string of type
<literal>'YYYY-MM-DD HH:MM:SS'</literal> and different timestamp
lengths are not supported.
@@ -92496,6 +92498,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="incompatiblechange"/>
<manual type="DOUBLE"/>
<manual type="FLOAT"/>
</tags>
@@ -92507,7 +92510,6 @@
<message>
<para>
- <emphasis role="bold">Warning: Incompatible change:</emphasis>
Handling of the <literal>FLOAT</literal> and
<literal>DOUBLE</literal> floating-point data types is more
strict to follow standard SQL. For example, a data type of
@@ -96243,6 +96245,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="incompatiblechange"/>
<manual type="Type"/>
<manual type="Engine"/>
<manual type="SHOW TABLE STATUS"/>
@@ -96255,7 +96258,6 @@
<message>
<para>
- <emphasis role="bold">Warning: Incompatible change:</emphasis>
The <literal>Type</literal> output column for <literal>SHOW
TABLE STATUS</literal> now is labeled <literal>Engine</literal>.
</para>
@@ -103421,6 +103423,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="incompatiblechange"/>
<manual type="NOT"/>
<manual type="HIGH_NOT_PRECEDENCE"/>
</tags>
@@ -103432,7 +103435,6 @@
<message>
<para>
- <emphasis role="bold">Warning: Incompatible change!</emphasis>
The precedence of <literal>NOT</literal> operator has changed so
that expressions such as <literal>NOT a BETWEEN b AND
c</literal> are parsed correctly as <literal>NOT (a BETWEEN b
@@ -115917,6 +115919,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="incompatiblechange"/>
<manual type="LOAD DATA INFILE"/>
<manual type="FIELDS ENCLOSED BY"/>
<manual type="mysqldump"/>
@@ -115936,8 +115939,7 @@
<message>
<para>
- <emphasis role="bold">Incompatible change:</emphasis> The
- behavior of <literal>LOAD DATA INFILE</literal> and
+ The behavior of <literal>LOAD DATA INFILE</literal> and
<literal>SELECT ... INTO OUTFILE</literal> has changed when the
<literal>FIELDS TERMINATED BY</literal> and <literal>FIELDS
ENCLOSED BY</literal> values both are empty. Formerly, a column
@@ -117154,6 +117156,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="incompatiblechange"/>
<manual type="mysqldump"/>
<manual type="MyISAM"/>
<manual type="InnoDB"/>
@@ -117172,7 +117175,6 @@
<message>
<para>
- <emphasis role="bold">Incompatible change:</emphasis>
<literal>MyISAM</literal> and <literal>InnoDB</literal> tables
created with <literal>DECIMAL</literal> columns in MySQL 5.0.3
to 5.0.5 will appear corrupt after an upgrade to MySQL 5.0.6.
@@ -119462,6 +119464,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="incompatiblechange"/>
<manual type="mysql_fix_privilege_tables"/>
<manual type="user"/>
</tags>
@@ -119473,7 +119476,6 @@
<message>
<para>
- <emphasis role="bold">Warning: Incompatible change:</emphasis>
Client authentication now is based on 41-byte passwords in the
<literal>user</literal> table, not 45-byte passwords as in
4.1.0. Any 45-byte passwords created for 4.1.0 must be reset
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r8995 - in trunk: . dynamic-docs/changelog | paul | 29 Nov |
