From: paul Date: April 12 2006 5:03pm Subject: svn commit - mysqldoc@docsrva: r1809 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-common List-Archive: http://lists.mysql.com/commits/4875 Message-Id: <200604121703.k3CH3INe032745@docsrva.mysql.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Author: paul Date: 2006-04-12 19:03:14 +0200 (Wed, 12 Apr 2006) New Revision: 1809 Log: r9407@frost: paul | 2006-04-12 11:59:38 -0500 Fixed-row format dump/reload behavior for LOAD DATA/SELECT ... INTO OUTFILE changed in 4.1.12/5.0.6: Declared display width is ignored. Instead a field large enough to hold all values is used. (Bug#12564) Modified: trunk/ trunk/refman-4.1/installing.xml trunk/refman-4.1/sql-syntax.xml trunk/refman-5.0/installing.xml trunk/refman-5.0/sql-syntax.xml trunk/refman-5.1/sql-syntax.xml trunk/refman-common/news-4.1.xml trunk/refman-common/news-5.0.xml Property changes on: trunk ___________________________________________________________________ Name: svk:merge - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:6598 b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:9405 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:4334 + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:6598 b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:9407 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:4334 Modified: trunk/refman-4.1/installing.xml =================================================================== --- trunk/refman-4.1/installing.xml 2006-04-12 15:47:59 UTC (rev 1808) +++ trunk/refman-4.1/installing.xml 2006-04-12 17:03:14 UTC (rev 1809) @@ -12664,6 +12664,29 @@ + Incompatible change: In + MySQL 4.1.12, the behavior of LOAD DATA + INFILE and SELECT ... INTO + OUTFILE has changed when the FIELDS + TERMINATED BY and FIELDS ENCLOSED + BY values both are empty. Formerly, a column was + read or written the display width of the column. For + example, INT(4) was read or written using + a field with a width of 4. Now columns are read and written + using a field width wide enough to hold all values in the + field. However, data files written before this change was + made might not be reloaded correctly with LOAD DATA + INFILE for MySQL 4.1.12 and up. This change also + affects data files read by mysqlimport + and written by mysqldump --tab, which use + LOAD DATA INFILE and SELECT ... + INTO OUTFILE. For more information, see + . + + + + + Incompatible change: Before MySQL 4.1.1, the statement parser was less strict and its string-to-date conversion would ignore everything up to the Modified: trunk/refman-4.1/sql-syntax.xml =================================================================== --- trunk/refman-4.1/sql-syntax.xml 2006-04-12 15:47:59 UTC (rev 1808) +++ trunk/refman-4.1/sql-syntax.xml 2006-04-12 17:03:14 UTC (rev 1809) @@ -5551,11 +5551,13 @@ (''), a fixed-row (non-delimited) format is used. With fixed-row format, no delimiters are used between fields (but you can still have a line terminator). - Instead, column values are written and read using the - display widths of the columns. For example, if a column is - declared as INT(7), values for the column - are written using seven-character fields. On input, values - for the column are obtained by reading seven characters. + Instead, column values are read and written using a field + width wide enough to hold all values in the field. For + TINYINT, SMALLINT, + MEDIUMINT, INT, and + BIGINT, the field widths are 4, 6, 8, 11, + and 20, respectively, no matter what the declared display + width is. @@ -5573,6 +5575,24 @@ that fixed-size format does not work if you are using a multi-byte character set. + + + Note: Before MySQL 4.1.12, + fixed-row format used the display width of the column. For + example, INT(4) was read or written using + a field with a width of 4. However, if the column contained + wider values, they were dumped to their full width, leading + to the possibility of a ragged field holding + values of different widths. Using a field wide enough to + hold all values in the field prevents this problem. However, + data files written before this change was made might not be + reloaded correctly with LOAD DATA INFILE + for MySQL 4.1.12 and up. This change also affects data files + read by mysqlimport and written by + mysqldump --tab, which use LOAD + DATA INFILE and SELECT ... INTO + OUTFILE. + Modified: trunk/refman-5.0/installing.xml =================================================================== --- trunk/refman-5.0/installing.xml 2006-04-12 15:47:59 UTC (rev 1808) +++ trunk/refman-5.0/installing.xml 2006-04-12 17:03:14 UTC (rev 1809) @@ -12381,6 +12381,30 @@ + Incompatible change: In + MySQL 4.1.12/5.0.6, the behavior of LOAD DATA + INFILE and SELECT ... INTO + OUTFILE has changed when the FIELDS + TERMINATED BY and FIELDS ENCLOSED + BY values both are empty. Formerly, a column was + read or written the display width of the column. For + example, INT(4) was read or written using + a field with a width of 4. Now columns are read and written + using a field width wide enough to hold all values in the + field. However, data files written before this change was + made might not be reloaded correctly with LOAD DATA + INFILE for MySQL 4.1.12/5.0.6 and up. This change + also affects data files read by + mysqlimport and written by + mysqldump --tab, which use LOAD + DATA INFILE and SELECT ... INTO + OUTFILE. For more information, see + . + + + + + Some keywords are reserved in MySQL ¤t-series; that were not reserved in MySQL &previous-series;. See . Modified: trunk/refman-5.0/sql-syntax.xml =================================================================== --- trunk/refman-5.0/sql-syntax.xml 2006-04-12 15:47:59 UTC (rev 1808) +++ trunk/refman-5.0/sql-syntax.xml 2006-04-12 17:03:14 UTC (rev 1809) @@ -5448,11 +5448,13 @@ (''), a fixed-row (non-delimited) format is used. With fixed-row format, no delimiters are used between fields (but you can still have a line terminator). - Instead, column values are written and read using the - display widths of the columns. For example, if a column is - declared as INT(7), values for the column - are written using seven-character fields. On input, values - for the column are obtained by reading seven characters. + Instead, column values are read and written using a field + width wide enough to hold all values in the field. For + TINYINT, SMALLINT, + MEDIUMINT, INT, and + BIGINT, the field widths are 4, 6, 8, 11, + and 20, respectively, no matter what the declared display + width is. @@ -5470,6 +5472,24 @@ that fixed-size format does not work if you are using a multi-byte character set. + + + Note: Before MySQL 5.0.6, + fixed-row format used the display width of the column. For + example, INT(4) was read or written using + a field with a width of 4. However, if the column contained + wider values, they were dumped to their full width, leading + to the possibility of a ragged field holding + values of different widths. Using a field wide enough to + hold all values in the field prevents this problem. However, + data files written before this change was made might not be + reloaded correctly with LOAD DATA INFILE + for MySQL 5.0.6 and up. This change also affects data files + read by mysqlimport and written by + mysqldump --tab, which use LOAD + DATA INFILE and SELECT ... INTO + OUTFILE. + Modified: trunk/refman-5.1/sql-syntax.xml =================================================================== --- trunk/refman-5.1/sql-syntax.xml 2006-04-12 15:47:59 UTC (rev 1808) +++ trunk/refman-5.1/sql-syntax.xml 2006-04-12 17:03:14 UTC (rev 1809) @@ -6701,11 +6701,13 @@ (''), a fixed-row (non-delimited) format is used. With fixed-row format, no delimiters are used between fields (but you can still have a line terminator). - Instead, column values are written and read using the - display widths of the columns. For example, if a column is - declared as INT(7), values for the column - are written using seven-character fields. On input, values - for the column are obtained by reading seven characters. + Instead, column values are read and written using a field + width wide enough to hold all values in the field. For + TINYINT, SMALLINT, + MEDIUMINT, INT, and + BIGINT, the field widths are 4, 6, 8, 11, + and 20, respectively, no matter what the declared display + width is. Modified: trunk/refman-common/news-4.1.xml =================================================================== --- trunk/refman-common/news-4.1.xml 2006-04-12 15:47:59 UTC (rev 1808) +++ trunk/refman-common/news-4.1.xml 2006-04-12 17:03:14 UTC (rev 1809) @@ -190,7 +190,7 @@ - + NDB Cluster: In a 2-node cluster with a @@ -199,14 +199,13 @@ to come up partitioned (split-brain issue). (Bug #16447) - + - A similar issue could occur when the cluster was first - started with a sufficiently low value for this parameter. (Bug - #18612) + A similar issue could occur when the cluster was first started + with a sufficiently low value for this parameter. (Bug #18612) - + NDB Cluster: On systems with multiple @@ -3916,6 +3915,28 @@ + Incompatible change: The + behavior of LOAD DATA INFILE and + SELECT ... INTO OUTFILE has changed when + the FIELDS TERMINATED BY and + FIELDS ENCLOSED BY values both are empty. + Formerly, a column was read or written the display width of + the column. For example, INT(4) was read or + written using a field with a width of 4. Now columns are read + and written using a field width wide enough to hold all values + in the field. However, data files written before this change + was made might not be reloaded correctly with LOAD + DATA INFILE for MySQL 4.1.12 and up. This change + also affects data files read by mysqlimport + and written by mysqldump --tab, which use + LOAD DATA INFILE and SELECT ... + INTO OUTFILE. For more information, see + . (Bug#12564) + + + + + Added option to my_print_defaults. Modified: trunk/refman-common/news-5.0.xml =================================================================== --- trunk/refman-common/news-5.0.xml 2006-04-12 15:47:59 UTC (rev 1808) +++ trunk/refman-common/news-5.0.xml 2006-04-12 17:03:14 UTC (rev 1809) @@ -191,13 +191,13 @@ Uncomment following when there are new features or feature changes to report. - + Functionality added or changed: - + - + NDB Cluster: It is now possible to perform @@ -206,7 +206,7 @@ all configured data nodes first. (Bug #18606) - + @@ -214,7 +214,7 @@ - + NDB Cluster: In a 2-node cluster with a @@ -223,14 +223,13 @@ to come up partitioned (split-brain issue). (Bug #16447) - + - A similar issue could occur when the cluster was first - started with a sufficiently low value for this parameter. (Bug - #18612) + A similar issue could occur when the cluster was first started + with a sufficiently low value for this parameter. (Bug #18612) - + NDB Cluster: On systems with multiple @@ -241,7 +240,7 @@ temporary outage. (Bug #15695) - + NDB Cluster: Unused open handlers for @@ -250,7 +249,7 @@ following an ALTER TABLE. (Bug #13228) - + NDB Cluster: Uninitialised internal @@ -9392,6 +9391,28 @@ + Incompatible change: The + behavior of LOAD DATA INFILE and + SELECT ... INTO OUTFILE has changed when + the FIELDS TERMINATED BY and + FIELDS ENCLOSED BY values both are empty. + Formerly, a column was read or written the display width of + the column. For example, INT(4) was read or + written using a field with a width of 4. Now columns are read + and written using a field width wide enough to hold all values + in the field. However, data files written before this change + was made might not be reloaded correctly with LOAD + DATA INFILE for MySQL 4.1.12 and up. This change + also affects data files read by mysqlimport + and written by mysqldump --tab, which use + LOAD DATA INFILE and SELECT ... + INTO OUTFILE. For more information, see + . (Bug#12564) + + + + + The precision of the DECIMAL data type has been increased from 64 to 65 decimal digits.