From: Date: October 17 2008 8:34pm Subject: svn commit - mysqldoc@docsrva: r12088 - in trunk: . dynamic-docs/changelog refman-5.1 refman-6.0 List-Archive: http://lists.mysql.com/commits/56492 Message-Id: <200810171834.m9HIYKjr006734@docsrva.mysql.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Author: paul Date: 2008-10-17 20:34:19 +0200 (Fri, 17 Oct 2008) New Revision: 12088 Log: r34822@dhcp-100: paul | 2008-10-17 13:27:32 -0500 Add versions to changelog entries Modified: trunk/dynamic-docs/changelog/mysqld-1.xml trunk/dynamic-docs/changelog/mysqld.xml trunk/refman-5.1/dba-core.xml trunk/refman-5.1/installing-core.xml trunk/refman-6.0/dba-core.xml trunk/refman-6.0/installing-core.xml Property changes on: trunk ___________________________________________________________________ Name: svk:merge - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828 7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:34797 b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:33695 + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828 7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:34822 b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:33695 Modified: trunk/dynamic-docs/changelog/mysqld-1.xml =================================================================== --- trunk/dynamic-docs/changelog/mysqld-1.xml 2008-10-17 16:08:37 UTC (rev 12087) +++ trunk/dynamic-docs/changelog/mysqld-1.xml 2008-10-17 18:34:19 UTC (rev 12088) Changed blocks: 39, Lines Added: 113, Lines Deleted: 2; 7710 bytes @@ -469,6 +469,7 @@ + @@ -28979,6 +28980,7 @@ + @@ -29005,6 +29007,7 @@ + @@ -29035,6 +29038,7 @@ + @@ -29062,6 +29066,7 @@ + @@ -29115,6 +29120,7 @@ + @@ -29141,6 +29147,7 @@ + @@ -29170,6 +29177,7 @@ + @@ -29814,6 +29822,7 @@ + @@ -29870,6 +29879,7 @@ + @@ -29896,6 +29906,7 @@ + @@ -29924,6 +29935,7 @@ + @@ -29951,6 +29963,7 @@ + @@ -29980,6 +29993,7 @@ + @@ -30007,6 +30021,7 @@ + @@ -30036,6 +30051,7 @@ + @@ -30062,6 +30078,7 @@ + @@ -30088,6 +30105,7 @@ + @@ -30113,6 +30131,7 @@ + @@ -30139,6 +30158,7 @@ + @@ -30165,6 +30185,7 @@ + @@ -30192,6 +30213,7 @@ + @@ -30220,6 +30242,7 @@ + @@ -30251,6 +30274,7 @@ + @@ -30278,6 +30302,7 @@ + @@ -30304,6 +30329,7 @@ + @@ -30332,6 +30358,7 @@ + @@ -30357,6 +30384,7 @@ + @@ -30384,6 +30412,7 @@ + @@ -30499,9 +30528,10 @@ + - + In connection with view creation, the server created @@ -30536,7 +30566,7 @@ - Downgrade to an older 5.1.X server and run + Downgrade to an older 5.1.x server and run mysql_upgrade. @@ -30575,6 +30605,80 @@ + + + + In connection with view creation, the server created + arc directories inside database directories + and maintained useless copies of .frm files + there. Creation and renaming procedures of those copies as well + as creation of arc directories has been + discontinued. + + + + This change does cause a problem when downgrading to older + server versions which manifests itself under these + circumstances: + + + + + + + Create a view v_orig in MySQL 6.0.8 or + higher. + + + + + + Rename the view to v_new and then back to + v_orig. + + + + + + Downgrade to an older 6.0.x server and run + mysql_upgrade. + + + + + + Try to rename v_orig to + v_new again. This operation fails. + + + + + + + As a workaround to avoid this problem, use either of these + approaches: + + + + + + + Dump your data using mysqldump before + downgrading and reload the dump file after downgrading. + + + + + + Instead of renaming a view after the downgrade, drop it and + recreate it. + + + + + + + @@ -30593,6 +30697,7 @@ + @@ -30622,6 +30727,7 @@ + @@ -30650,6 +30756,7 @@ + @@ -30675,6 +30782,7 @@ + @@ -30729,6 +30837,7 @@ + @@ -30754,6 +30863,7 @@ + @@ -30817,6 +30927,7 @@ + Modified: trunk/dynamic-docs/changelog/mysqld.xml =================================================================== --- trunk/dynamic-docs/changelog/mysqld.xml 2008-10-17 16:08:37 UTC (rev 12087) +++ trunk/dynamic-docs/changelog/mysqld.xml 2008-10-17 18:34:19 UTC (rev 12088) Changed blocks: 1, Lines Added: 1, Lines Deleted: 0; 447 bytes @@ -39798,6 +39798,7 @@ + Modified: trunk/refman-5.1/dba-core.xml =================================================================== --- trunk/refman-5.1/dba-core.xml 2008-10-17 16:08:37 UTC (rev 12087) +++ trunk/refman-5.1/dba-core.xml 2008-10-17 18:34:19 UTC (rev 12088) Changed blocks: 4, Lines Added: 12, Lines Deleted: 9; 2609 bytes @@ -458,8 +458,9 @@ Specify whether to use row-based, statement-based, or mixed replication (statement-based was the default prior to MySQL - 5.1.12; beginning with MySQL 5.1.12, mixed replication is - the default). See . + 5.1.12; in 5.1.12, the default was changed to mixed + replication; in 5.1.29, the default was changed back to + statement-based). See . This option was added in MySQL 5.1.5. @@ -3966,8 +3967,9 @@ STATEMENT was used by default prior to - MySQL 5.1.12; beginning with MySQL 5.1.12, - MIXED is the default. When + MySQL 5.1.12; in 5.1.12, the default was changed to mixed + MIXED; in 5.1.29, the default was changed + back to STATEMENT. When MIXED is specified, statement-based replication is used, except for cases where only row-based replication is guaranteed to lead to proper results. For @@ -13948,9 +13950,10 @@ - Mixed logging is available beginning with MySQL 5.1.8. - Beginning with MySQL 5.1.12, it is the default logging - mode. + Mixed logging is available beginning with MySQL 5.1.8. In + MySQL 5.1.12, it become the default logging mode; in + 5.1.29, the default was changed back to + STATEMENT. @@ -14015,14 +14018,14 @@ STATEMENT causes replication to be statement-based. This is the default for MySQL 5.1.11 - and earlier. + and earlier, and MySQL 5.1.29 and later. MIXED causes replication to use mixed - format. This is the default for MySQL 5.1.12 and later. + format. This is the default for MySQL 5.1.12 to 5.1.28. Modified: trunk/refman-5.1/installing-core.xml =================================================================== --- trunk/refman-5.1/installing-core.xml 2008-10-17 16:08:37 UTC (rev 12087) +++ trunk/refman-5.1/installing-core.xml 2008-10-17 18:34:19 UTC (rev 12088) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 547 bytes @@ -12772,7 +12772,7 @@ - Downgrade to an older 5.1.X server and run + Downgrade to an older 5.1.x server and run mysql_upgrade. Modified: trunk/refman-6.0/dba-core.xml =================================================================== --- trunk/refman-6.0/dba-core.xml 2008-10-17 16:08:37 UTC (rev 12087) +++ trunk/refman-6.0/dba-core.xml 2008-10-17 18:34:19 UTC (rev 12088) Changed blocks: 3, Lines Added: 6, Lines Deleted: 3; 1367 bytes @@ -486,7 +486,8 @@ Specify whether to use row-based, statement-based, or mixed - replication (mixed is the default). See + replication (mixed is the default before MySQL 6.0.8 and + statement-based as of 6.0.8). See . @@ -3938,7 +3939,8 @@ - MIXED is used by default. If + MIXED is used by default. before MySQL + 6.0.8 and STATEMENT as of 6.0.8. If MIXED is specified, statement-based replication is used, too, except for cases where only row-based replication is guaranteed to lead to proper @@ -13850,7 +13852,8 @@ Setting The Binary Log Format - The default binary logging format is mixed-based. + The default binary logging format is mixed-based before MySQL + 6.0.8 and statement-based as of 6.0.8. Modified: trunk/refman-6.0/installing-core.xml =================================================================== --- trunk/refman-6.0/installing-core.xml 2008-10-17 16:08:37 UTC (rev 12087) +++ trunk/refman-6.0/installing-core.xml 2008-10-17 18:34:19 UTC (rev 12088) Changed blocks: 1, Lines Added: 73, Lines Deleted: 0; 2708 bytes @@ -12703,6 +12703,79 @@ + In connection with view creation, the server created + arc directories inside database + directories and maintained useless copies of + .frm files there. Creation and renaming + procedures of those copies as well as creation of + arc directories has been discontinued + in MySQL 6.0.8. + + + + This change does cause a problem when downgrading to older + server versions which manifests itself under these + circumstances: + + + + + + + Create a view v_orig in MySQL 6.0.8 + or higher. + + + + + + Rename the view to v_new and then + back to v_orig. + + + + + + Downgrade to an older 6.0.x server and run + mysql_upgrade. + + + + + + Try to rename v_orig to + v_new again. This operation fails. + + + + + + + As a workaround to avoid this problem, use either of these + approaches: + + + + + + + Dump your data using mysqldump before + downgrading and reload the dump file after downgrading. + + + + + + Instead of renaming a view after the downgrade, drop it + and recreate it. + + + + + + + + Incompatible change: In MySQL 6.0.6, a change was made to the way that the server handles prepared statements. This affects prepared