svn commit - mysqldoc@oter02: r26254 - in trunk: . dynamic-docs/changelog refman-5.5

[paul.dubois]

Author: pd221994
Date: 2011-05-17 21:25:58 +0200 (Tue, 17 May 2011)
New Revision: 26254

Log:
 r48065@dhcp-adc-twvpn-1-vpnpool-10-154-25-110:  paul | 2011-05-17 11:05:04 -0500
 Point out possible surprise about charset autodetection, how to get previous
 behavior


Modified:
   svk:merge
   trunk/dynamic-docs/changelog/mysqld-1.xml
   trunk/refman-5.5/internationalization.xml

Property changes on: trunk
___________________________________________________________________

Modified: svk:merge
===================================================================


Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 1277 bytes


Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml	2011-05-17 19:25:50 UTC (rev 26253)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml	2011-05-17 19:25:58 UTC (rev 26254)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 1; 709 bytes

@@ -73157,7 +73157,9 @@
         client programs will use a different connection character set
         than previously, as though you had issued an implicit
         <literal role="stmt" condition="set-option">SET NAMES</literal>
-        statement.
+        statement. If the previous behavior is required, start the
+        client with the <option>--default-character-set=latin1</option>
+        option.
       </para>
 
       <para>


Modified: trunk/refman-5.5/internationalization.xml
===================================================================
--- trunk/refman-5.5/internationalization.xml	2011-05-17 19:25:50 UTC (rev 26253)
+++ trunk/refman-5.5/internationalization.xml	2011-05-17 19:25:58 UTC (rev 26254)
Changed blocks: 1, Lines Added: 16, Lines Deleted: 0; 1264 bytes

@@ -1674,6 +1674,22 @@
 
       </itemizedlist>
 
+      <note>
+        <para>
+          Before MySQL &current-series;, in the absence of other
+          information, the MySQL client programs used the compiled-in
+          default character set, usually <literal>latin1</literal>. An
+          implication of this difference is that if your environment is
+          configured to use a non-<literal>latin1</literal> locale,
+          MySQL client programs will use a different connection
+          character set than previously, as though you had issued an
+          implicit <literal role="stmt" condition="set-option">SET
+          NAMES</literal> statement. If the previous behavior is
+          required, start the client with the
+          <option>--default-character-set=latin1</option> option.
+        </para>
+      </note>
+
       <para>
         When a client connects to the server, it sends the name of the
         character set that it wants to use. The server uses the name to