MySQL Lists are EOL. Please join:

List:Commits« Previous MessageNext Message »
From:paul Date:December 19 2007 5:48am
Subject:svn commit - mysqldoc@docsrva: r9392 - in trunk: . dynamic-docs/changelog refman-5.0 refman-5.1 refman-6.0
View as plain text  
Author: paul
Date: 2007-12-19 06:48:41 +0100 (Wed, 19 Dec 2007)
New Revision: 9392

Log:
 r28282@frost:  paul | 2007-12-18 23:45:18 -0600
 Document bugfixes:
 Bug #32198	Comparison of DATE with DATETIME still not using indexes correctly
 Bug #29323	mysql client only accetps ANSI encoded files
 (now mysql ignores BOM characters at the beginning of input files)


Modified:
   trunk/dynamic-docs/changelog/mysqld-1.xml
   trunk/dynamic-docs/changelog/mysqld.xml
   trunk/refman-5.0/programs-client.xml
   trunk/refman-5.1/programs-client.xml
   trunk/refman-6.0/programs-client.xml

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:34416
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:28275
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:22582
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:34416
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:28282
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:22582


Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml	2007-12-19 03:23:21 UTC (rev 9391)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml	2007-12-19 05:48:41 UTC (rev 9392)
Changed blocks: 1, Lines Added: 79, Lines Deleted: 0; 2470 bytes

@@ -3631,4 +3631,83 @@
 
   </logentry>
 
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="mysql"/>
+      <manual type="Unicode"/>
+      <manual type="byte order mark"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="29323"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.0.54"/>
+      <version ver="5.1.23"/>
+      <version ver="6.0.4"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The <command>mysql</command> client program now ignores Unicode
+        byte order mark (BOM) characters at the beginning of input
+        files. Previously, it read them and sent them to the server,
+        resulting in a syntax error.
+      </para>
+
+      <para>
+        Presence of a BOM does not cause <command>mysql</command> to
+        change its default character set. To do that, invoke
+        <command>mysql</command> with an option such as
+        <option>--default-character-set=utf8</option>.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="DATE"/>
+      <manual type="DATETIME"/>
+      <manual type="optimizer"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="32198"/>
+      <seealsobug bugid="27590"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.0.54"/>
+      <version ver="5.1.23"/>
+      <version ver="6.0.5"/>
+    </versions>
+
+    <message>
+
+      <para>
+        For comparisons of the form <replaceable>date_col OP
+        datetime_const</replaceable> (where
+        <replaceable>OP</replaceable> is
+        <function role="sqlop" condition="equal">=</function>,
+        <function role="sqlop" condition="less-than">&lt;</function>,
+        <function role="sqlop" condition="greater-than">&gt;</function>,
+        <function role="sqlop" condition="less-than-or-equal">&lt;=</function>,
+        or
+        <function role="sqlop" condition="greater-than-or-equal">&gt;=</function>),
+        the comparison is done using <literal>DATETIME</literal> values,
+        per the fix for Bug#27590. However that fix caused any index on
+        <replaceable>date_col</replaceable> not to be used and
+        compromised performance. Now the index is used again.
+      </para>
+
+    </message>
+
+  </logentry>
+
 </changelog>


Modified: trunk/dynamic-docs/changelog/mysqld.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld.xml	2007-12-19 03:23:21 UTC (rev 9391)
+++ trunk/dynamic-docs/changelog/mysqld.xml	2007-12-19 05:48:41 UTC (rev 9392)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 0; 400 bytes

@@ -132081,6 +132081,7 @@
 
     <bugs>
       <fixes bugid="27590"/>
+      <seealsobug bugid="32198"/>
     </bugs>
 
     <versions>


Modified: trunk/refman-5.0/programs-client.xml
===================================================================
--- trunk/refman-5.0/programs-client.xml	2007-12-19 03:23:21 UTC (rev 9391)
+++ trunk/refman-5.0/programs-client.xml	2007-12-19 05:48:41 UTC (rev 9392)
Changed blocks: 1, Lines Added: 10, Lines Deleted: 0; 919 bytes

@@ -2282,6 +2282,16 @@
       </para>
 
       <para>
+        As of MySQL 5.0.54, <command>mysql</command> ignores Unicode byte
+        order mark (BOM) characters at the beginning of input files.
+        Previously, it read them and sent them to the server, resulting
+        in a syntax error. Presence of a BOM does not cause
+        <command>mysql</command> to change its default character set. To
+        do that, invoke <command>mysql</command> with an option such as
+        <option>--default-character-set=utf8</option>.
+      </para>
+
+      <para>
         For more information about batch mode, see
         <xref linkend="batch-mode"/>.
       </para>


Modified: trunk/refman-5.1/programs-client.xml
===================================================================
--- trunk/refman-5.1/programs-client.xml	2007-12-19 03:23:21 UTC (rev 9391)
+++ trunk/refman-5.1/programs-client.xml	2007-12-19 05:48:41 UTC (rev 9392)
Changed blocks: 1, Lines Added: 10, Lines Deleted: 0; 919 bytes

@@ -2335,6 +2335,16 @@
       </para>
 
       <para>
+        As of MySQL 5.1.23, <command>mysql</command> ignores Unicode byte
+        order mark (BOM) characters at the beginning of input files.
+        Previously, it read them and sent them to the server, resulting
+        in a syntax error. Presence of a BOM does not cause
+        <command>mysql</command> to change its default character set. To
+        do that, invoke <command>mysql</command> with an option such as
+        <option>--default-character-set=utf8</option>.
+      </para>
+
+      <para>
         For more information about batch mode, see
         <xref linkend="batch-mode"/>.
       </para>


Modified: trunk/refman-6.0/programs-client.xml
===================================================================
--- trunk/refman-6.0/programs-client.xml	2007-12-19 03:23:21 UTC (rev 9391)
+++ trunk/refman-6.0/programs-client.xml	2007-12-19 05:48:41 UTC (rev 9392)
Changed blocks: 1, Lines Added: 10, Lines Deleted: 0; 918 bytes

@@ -2313,6 +2313,16 @@
       </para>
 
       <para>
+        As of MySQL 6.0.4, <command>mysql</command> ignores Unicode byte
+        order mark (BOM) characters at the beginning of input files.
+        Previously, it read them and sent them to the server, resulting
+        in a syntax error. Presence of a BOM does not cause
+        <command>mysql</command> to change its default character set. To
+        do that, invoke <command>mysql</command> with an option such as
+        <option>--default-character-set=utf8</option>.
+      </para>
+
+      <para>
         For more information about batch mode, see
         <xref linkend="batch-mode"/>.
       </para>


Thread
svn commit - mysqldoc@docsrva: r9392 - in trunk: . dynamic-docs/changelog refman-5.0 refman-5.1 refman-6.0paul19 Dec