From: paul
Date: December 14 2005 5:37pm
Subject: svn commit - mysqldoc@docsrva: r560 - in trunk: . refman-4.1 refman-5.0 refman-common
List-Archive: http://lists.mysql.com/commits/161
Message-Id: <200512141737.jBEHbS61030267@docsrva.mysql.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Author: paul
Date: 2005-12-14 18:37:24 +0100 (Wed, 14 Dec 2005)
New Revision: 560
Log:
r4768@frost: paul | 2005-12-14 11:32:31 -0600
Note stricter handling of FLOAT/DOUBLE data types in 4.1.2 and up.
Note stricter handling of DECIMAL/NUMERIC data types in 5.0.3 and up.
In change lists, float some incompatible changes to the front of the list.
Modified:
trunk/
trunk/refman-4.1/installing.xml
trunk/refman-5.0/installing.xml
trunk/refman-common/news-4.1.xml
trunk/refman-common/news-5.0.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:4743
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1648
+ b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:4768
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1648
Modified: trunk/refman-4.1/installing.xml
===================================================================
--- trunk/refman-4.1/installing.xml 2005-12-14 14:45:22 UTC (rev 559)
+++ trunk/refman-4.1/installing.xml 2005-12-14 17:37:24 UTC (rev 560)
@@ -12489,6 +12489,37 @@
+ Warning: Incompatible
+ change: As of MySQL 4.1.2, handling of the
+ FLOAT and DOUBLE
+ floating-point data types is more strict to follow standard
+ SQL. For example, a data type of
+ FLOAT(3,1) stores a maximum value of
+ 99.9. Before 4.1.2, the server allowed larger numbers to be
+ stored. That is, it stored a value such as 100.0 as 100.0.
+ As of 4.1.2, the server clips clips 100.0 to the maximum
+ allowable value of 99.9. If you have tables that were
+ created before MySQL 4.1.2 and that contain floating-point
+ data not strictly legal for the column type, you should
+ alter the data types of those columns. For example:
+
+
+
+ALTER TABLE tbl_name MODIFY col_name FLOAT(4,1);
+
+
+
+
+
+ Incompatible change: In
+ connection with the support for per-connection time zones in
+ MySQL 4.1.3, the timezone system variable
+ was renamed to system_time_zone.
+
+
+
+
+ Important note: MySQL 4.1
stores table names and column names in
UTF8. If you have table names or column
@@ -12515,15 +12546,6 @@
- Incompatible change: In
- connection with the support for per-connection time zones in
- MySQL 4.1.3, the timezone system variable
- was renamed to system_time_zone.
-
-
-
-
-
All tables and non-binary string columns
(CHAR, VARCHAR, and
TEXT) have a character set. See
Modified: trunk/refman-5.0/installing.xml
===================================================================
--- trunk/refman-5.0/installing.xml 2005-12-14 14:45:22 UTC (rev 559)
+++ trunk/refman-5.0/installing.xml 2005-12-14 17:37:24 UTC (rev 560)
@@ -12225,15 +12225,35 @@
downgrade to MySQL 5.0.3 to 5.0.5.)
-
+
- Incompatible change:
- The implementation of DECIMAL has changed
- in MySQL 5.0.3. You should make your applications aware of
- that change, which is described in
+ Incompatible change: The
+ implementation of DECIMAL has changed in
+ MySQL 5.0.3. You should make your applications aware of that
+ change, which is described in
.
+
+
+ A consequence of the change in handling of the
+ DECIMAL and NUMERIC
+ fixed-point data types is that the server is more strict to
+ follow standard SQL. For example, a data type of
+ DECIMAL(3,1) stores a maximum value of
+ 99.9. Before MySQL 5.0.3, the server allowed larger numbers
+ to be stored. That is, it stored a value such as 100.0 as
+ 100.0. As of MySQL 5.0.3, the server clips clips 100.0 to
+ the maximum allowable value of 99.9. If you have tables that
+ were created before MySQL 5.0.3 and that contain
+ floating-point data not strictly legal for the column type,
+ you should alter the data types of those columns. For
+ example:
+
+
+
+ALTER TABLE tbl_name MODIFY col_name DECIMAL(4,1);
+
Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml 2005-12-14 14:45:22 UTC (rev 559)
+++ trunk/refman-common/news-4.1.xml 2005-12-14 17:37:24 UTC (rev 560)
@@ -7461,29 +7461,26 @@
- Added the ARCHIVE storage engine.
+ Warning: Incompatible change;
+ C API change: mysql_shutdown() 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 with older
+ servers. See .
- Added SQL syntax for prepared statements. See
- .
+ Warning: Incompatible change:
+ The timezone system variable has been
+ removed and replaced by system_time_zone.
+ See .
- Language-specific collations were added for the
- ucs2 and utf8 Unicode
- character sets: Icelandic, Latvian, Romanian, Slovenian,
- Polish, Estonian, Swedish, Turkish, Czech, Danish, Lithuanian,
- Slovak, Spanish, Traditional Spanish.
-
-
-
-
-
Support for per-connection time zones was added. Now you can
set the current time zone for a connection by setting the
@@time_zone system variable to a value such
@@ -7507,15 +7504,6 @@
- Warning: Incompatible change!
- The timezone system variable has been
- removed and replaced by system_time_zone.
- See .
-
-
-
-
-
Basic time zone conversion function
CONVERT_TZ() was added. It assumes that its
first argument is a datetime value in the time zone specified
@@ -7526,24 +7514,36 @@
- CHECK TABLE now can be killed. It then
- marks the table as corrupted. See .
+ Added the ARCHIVE storage engine.
- Warning: Incompatible change!
- C API change: mysql_shutdown() 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 with older
- servers. See .
+ Added SQL syntax for prepared statements. See
+ .
+ Language-specific collations were added for the
+ ucs2 and utf8 Unicode
+ character sets: Icelandic, Latvian, Romanian, Slovenian,
+ Polish, Estonian, Swedish, Turkish, Czech, Danish, Lithuanian,
+ Slovak, Spanish, Traditional Spanish.
+
+
+
+
+
+ CHECK TABLE now can be killed. It then
+ marks the table as corrupted. See .
+
+
+
+
+ OPTIMIZE TABLE for
InnoDB tables is now mapped to
ALTER TABLE instead of ANALYZE
@@ -7898,86 +7898,28 @@
- Added the EXAMPLE storage engine.
+ Warning: Incompatible change:
+ Handling of the FLOAT and
+ DOUBLE floating-point data types is more
+ strict to follow standard SQL. For example, a data type of
+ FLOAT(3,1) stores a maximum value of 99.9.
+ Previously, the server allowed larger numbers to be stored.
+ That is, it stored a value such as 100.0 as 100.0. Now the
+ server clips clips 100.0 to the maximum allowable value of
+ 99.9. If you have tables that were created before MySQL 4.1.2
+ and that contain floating-point data not strictly legal for
+ the column type, you should alter the data types of those
+ columns. For example:
-
-
-
- The mysqld Windows server was renamed to
- mysqld-debug. See
- .
-
+
+ALTER TABLE tbl_name MODIFY col_name FLOAT(4,1);
+
- Added Handler_discover status variable.
-
-
-
-
-
- Added support for character set conversion and
- MYSQL_TYPE_BLOB type code in prepared
- statement protocol.
-
-
-
-
-
- Added explanation of hidden SELECT of
- UNION in output of EXPLAIN
- SELECT statement.
-
-
-
-
-
- mysql command-line client now supports
- multiple options. (Bug #591)
-
-
-
-
-
- New myisam_data_pointer_size system
- variable. See .
-
-
-
-
-
- The server option now is
- enabled by default. Disable with
- .
-
-
-
-
-
- The
-
- option now requires that the filename must exist (safety fix).
- (Bug #3413)
-
-
-
-
-
- mysqld_multi now creates the log in the
- directory named by datadir (from the
- [mysqld] section in
- my.cnf or compiled in), not in
- /tmp. Thanks to Christian Hammers from
- Debian Security Team for reporting this.
- (CAN-2004-0388)
-
-
-
-
-
- Warning: Incompatible change!
+ Warning: Incompatible change:
String comparison now works according to the SQL standard.
Because we have that 'a' = 'a ' then from
it must follow that 'a' > 'a\t'. (The
@@ -8013,7 +7955,7 @@
would be treated as a TIMESTAMP DEFAULT 0
column. NOW is supported as an alias for
CURRENT_TIMESTAMP.
- Warning: Incompatible change!
+ Warning: Incompatible change:
Unlike in previous versions, explicit specification of default
values for TIMESTAMP column is never
ignored and turns off the auto-set feature (unless you have
@@ -8023,7 +7965,7 @@
- Warning: Incompatible change!
+ Warning: Incompatible change:
Renamed prepared statements C API functions:
@@ -8089,7 +8031,7 @@
- Warning: Incompatible change!
+ Warning: Incompatible change:
The signature of the mysql_stmt_prepare()
function was changed to int
mysql_stmt_prepare(MYSQL_STMT *stmt, const char *query,
@@ -8102,6 +8044,94 @@
+ Warning: Incompatible change:
+ The Type output column for SHOW
+ TABLE STATUS now is labeled
+ Engine.
+
+
+
+
+
+ Added the EXAMPLE storage engine.
+
+
+
+
+
+ The mysqld Windows server was renamed to
+ mysqld-debug. See
+ .
+
+
+
+
+
+ Added Handler_discover status variable.
+
+
+
+
+
+ Added support for character set conversion and
+ MYSQL_TYPE_BLOB type code in prepared
+ statement protocol.
+
+
+
+
+
+ Added explanation of hidden SELECT of
+ UNION in output of EXPLAIN
+ SELECT statement.
+
+
+
+
+
+ mysql command-line client now supports
+ multiple options. (Bug #591)
+
+
+
+
+
+ New myisam_data_pointer_size system
+ variable. See .
+
+
+
+
+
+ The server option now is
+ enabled by default. Disable with
+ .
+
+
+
+
+
+ The
+
+ option now requires that the filename must exist (safety fix).
+ (Bug #3413)
+
+
+
+
+
+ mysqld_multi now creates the log in the
+ directory named by datadir (from the
+ [mysqld] section in
+ my.cnf or compiled in), not in
+ /tmp. Thanks to Christian Hammers from
+ Debian Security Team for reporting this.
+ (CAN-2004-0388)
+
+
+
+
+ SHOW GRANTS with no FOR
clause or with FOR CURRENT_USER() shows the
privileges for the current session.
@@ -8280,15 +8310,6 @@
- Warning: Incompatible change!
- The Type output column for SHOW
- TABLE STATUS now is labeled
- Engine.
-
-
-
-
-
Added init_connect and
init_slave system variables. The values
should be SQL statements to be executed when each client
@@ -9397,17 +9418,7 @@
- Important note: If you
- upgrade to InnoDB-4.1.1 or higher, you
- cannot downgrade to a version lower than 4.1.1 any more! That
- is because earlier versions of InnoDB are
- not aware of multiple tablespaces.
-
-
-
-
-
- Warning: Incompatible change!
+ Warning: Incompatible change:
Renamed the C API mysql_prepare_result()
function to mysql_get_metadata() because
the old name was confusing.
@@ -9416,7 +9427,7 @@
- Warning: Incompatible change!
+ Warning: Incompatible change:
Client authentication now is based on 41-byte passwords in the
user table, not 45-byte passwords as in
4.1.0. Any 45-byte passwords created for 4.1.0 must be reset
@@ -9427,6 +9438,16 @@
+ Important note: If you
+ upgrade to InnoDB-4.1.1 or higher, you
+ cannot downgrade to a version lower than 4.1.1 any more! That
+ is because earlier versions of InnoDB are
+ not aware of multiple tablespaces.
+
+
+
+
+
Added secure_auth global server system
variable and server option that
disallow authentication for accounts that have old (pre-4.1.1)
@@ -10305,6 +10326,23 @@
+ Warning: Incompatible change:
+ TIMESTAMP is now returned as a string of
+ type 'YYYY-MM-DD HH:MM:SS' and different
+ timestamp lengths are not supported.
+
+
+
+ This change was necessary for SQL standards compliance. In a
+ future version, a further change will be made (backward
+ compatible with this change), allowing the timestamp length to
+ indicate the desired number of digits of fractions of a
+ second.
+
+
+
+
+
Renamed SHOW MASTER LOGS statement to
SHOW BINARY LOGS.
@@ -10501,23 +10539,6 @@
- Warning: Incompatible change!
- TIMESTAMP is now returned as a string of
- type 'YYYY-MM-DD HH:MM:SS' and different
- timestamp lengths are not supported.
-
-
-
- This change was necessary for SQL standards compliance. In a
- future version, a further change will be made (backward
- compatible with this change), allowing the timestamp length to
- indicate the desired number of digits of fractions of a
- second.
-
-
-
-
-
New faster client/server protocol that supports prepared
statements, bound parameters, and bound result columns, binary
transfer of data, warnings.
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2005-12-14 14:45:22 UTC (rev 559)
+++ trunk/refman-common/news-5.0.xml 2005-12-14 17:37:24 UTC (rev 560)
@@ -8410,6 +8410,35 @@
+ The DECIMAL and NUMERIC
+ data types now are handled with a fixed-point library that
+ allows for precision math handling that results in more
+ accurate results. See .
+
+
+
+ Warning: Incompatible change:
+ A consequence of the change in handling of the
+ DECIMAL and NUMERIC
+ fixed-point data types is that the server is more strict to
+ follow standard SQL. For example, a data type of
+ DECIMAL(3,1) stores a maximum value of
+ 99.9. Previously, the server allowed larger numbers to be
+ stored. That is, it stored a value such as 100.0 as 100.0. Now
+ the server clips clips 100.0 to the maximum allowable value of
+ 99.9. If you have tables that were created before MySQL 5.0.3
+ and that contain floating-point data not strictly legal for
+ the column type, you should alter the data types of those
+ columns. For example:
+
+
+
+ALTER TABLE tbl_name MODIFY col_name DECIMAL(4,1);
+
+
+
+
+ Incompatible change: The C
API ER_WARN_DATA_TRUNCATED warning symbol
was renamed to WARN_DATA_TRUNCATED.