| List: | Internals | « Previous MessageNext Message » | |
| From: | mhillyer | Date: | June 24 2005 7:41pm |
| Subject: | bk commit - mysqldoc@docsrva tree (Mike.Hillyer:1.2883) | ||
| View as plain text | |||
Below is the list of changes that have just been committed into a local mysqldoc repository of root. When root does a push these changes will be propagated to the main repository and, within 24 hours after the push, to the public repository. For information on how to access the public repository see http://www.mysql.com/doc/I/n/Installing_source_tree.html ChangeSet 1.2883 05/06/24 11:41:12 Mike.Hillyer@stripped +6 -0 Bugfix documenting. refman/news.xml 1.35 05/06/24 11:41:11 Mike.Hillyer@stripped +186 -150 Bug #7024 Bug #11325 Bug #11377 Bug #11185 Bug #11142 Bug #11283 refman/functions.xml 1.5 05/06/24 11:41:10 Mike.Hillyer@stripped +15 -1 Minor updates. refman-5.0/news.xml 1.30 05/06/24 11:41:10 Mike.Hillyer@stripped +186 -150 Sync refman-5.0/functions.xml 1.5 05/06/24 11:41:10 Mike.Hillyer@stripped +15 -1 Sync refman-4.1/news.xml 1.30 05/06/24 11:41:10 Mike.Hillyer@stripped +186 -150 Sync refman-4.1/functions.xml 1.5 05/06/24 11:41:10 Mike.Hillyer@stripped +15 -1 Sync # This is a BitKeeper patch. What follows are the unified diffs for the # set of deltas contained in the patch. The rest of the patch, the part # that BitKeeper cares about, is below these diffs. # User: Mike.Hillyer # Host: www.openwin.org # Root: /home/mysqldoc/mysqldoc --- 1.4/refman-4.1/functions.xml 2005-06-23 16:01:05 -06:00 +++ 1.5/refman-4.1/functions.xml 2005-06-24 11:41:10 -06:00 @@ -1028,7 +1028,13 @@ <literal>=</literal> is always false. </para> - <para>The <literal>ISNULL()</literal> function shares some special behaviors with the <literal>IS NULL</literal> comparison operator, see the description of <literal>IS NULL</literal> at <xref linkend="comparison-operators" />.</para> + <para> + The <literal>ISNULL()</literal> function shares some special + behaviors with the <literal>IS NULL</literal> comparison operator, + see the description of <literal>IS NULL</literal> at + <xref linkend="comparison-operators" />. + </para> + <para> <!-- description_for_help_topic INTERVAL --> </para> @@ -10354,6 +10360,10 @@ </para></listitem> <listitem><para> + <literal>DECIMAL</literal> + </para></listitem> + + <listitem><para> <literal>SIGNED [INTEGER]</literal> </para></listitem> @@ -10379,6 +10389,10 @@ available as of MySQL 4.0.2. The <literal>CHAR</literal> conversion type is available as of 4.0.6. The <literal>USING</literal> form of <literal>CONVERT()</literal> is available as of 4.1.0. + </para> + + <para> + The <literal>DECIMAL</literal> type is available as of MySQL 5.0.8. </para> <para> --- 1.29/refman-4.1/news.xml 2005-06-24 07:59:29 -06:00 +++ 1.30/refman-4.1/news.xml 2005-06-24 11:41:10 -06:00 @@ -206,32 +206,48 @@ </para> <section id="news-5-0-9"> - <title id="title-news-5-0-9">&title-news-5-0-9;</title> - <para> - Functionality added or changed: - </para> + <title id="title-news-5-0-9">&title-news-5-0-9;</title> - <itemizedlist> + <para> + Functionality added or changed: + </para> - <listitem> - <para></para> - </listitem> + <itemizedlist> - </itemizedlist> + <listitem><para></para></listitem> - <para> - Bugs fixed: - </para> + </itemizedlist> - <itemizedlist> + <para> + Bugs fixed: + </para> - <listitem> - <para>Clients would hang following some errors with stored - procedures. (Bug #9503)</para> - </listitem> + <itemizedlist> - </itemizedlist> + <listitem><para> + Optimizer performed range check when comparing unsigned integers to + negative constants, could cause errors. (Bug #11185) + </para></listitem> + + <listitem><para> + Wrong comparison method used in <literal>VIEW</literal> when + relaxed date syntax used (i.e. <literal>2005.06.10</literal>). (Bug + #11325) + </para></listitem> + + <listitem><para> + The <literal>ENCRYPT()</literal> and + <literal>SUBSTRING_INDEX()</literal> functions would cause errors + when used with a <literal>VIEW</literal>. (Bug #7024) + </para></listitem> + + <listitem><para> + Clients would hang following some errors with stored procedures. + (Bug #9503) + </para></listitem> + + </itemizedlist> </section> @@ -258,11 +274,10 @@ <itemizedlist> - <listitem> - <para><literal>MEMORY</literal> tables now support indexes of up - to 500 bytes. See <xref linkend="memory-storage-engine"/>. - (Bug #10566)</para> - </listitem> + <listitem><para> + <literal>MEMORY</literal> tables now support indexes of up to 500 + bytes. See <xref linkend="memory-storage-engine"/>. (Bug #10566) + </para></listitem> <listitem><para> New <literal>SQL_MODE</literal> - @@ -271,12 +286,12 @@ disabled or not compiled in. (Bug #6877) </para></listitem> - <listitem> - <para>The statements <literal>CREATE TABLE</literal>, - <literal>TRUNCATE TABLE</literal>, <literal>DROP - DATABASE</literal>, and <literal>CREATE DATABASE</literal> cause - an implicit commit. (Bug #6883)</para> - </listitem> + <listitem><para> + The statements <literal>CREATE TABLE</literal>, <literal>TRUNCATE + TABLE</literal>, <literal>DROP DATABASE</literal>, and + <literal>CREATE DATABASE</literal> cause an implicit commit. (Bug + #6883) + </para></listitem> <listitem><para> Expanded on information provided in general log and slow query log @@ -405,87 +420,95 @@ Thanks! --> + <listitem><para> + <literal>CAST( ... AS DECIMAL) didn't work for strings. (Bug + #11283)</literal> + </para></listitem> - <listitem> - <para>Setting <literal>@@SQL_MODE = NULL</literal> caused an - erroneous error message. (Bug #10732)</para> - </listitem> + <listitem><para> + <literal>NULLIF()</literal> function could produce incorrect + results if first argument is <literal>NULL</literal>. (Bug #11142) + </para></listitem> - <listitem> - <para>Converting a <literal>VARCHAR</literal> column having an - index to a different type (such as <literal>TINYTEXT</literal>) - gave rise to an incorrect error message. (Bug #10543)</para> - - <para>Note that this bugfix induces a slight change in the - behaviour of indexes: If an index is defined to be the same length - as a field (or is left to default to that field's length), and the - length of the field is later changed, then the index will adopt - the new length of the field. Previously, the size of the index did - not change for some field types (such as - <literal>VARCHAR</literal>) when the field type was - changed.</para> - </listitem> + <listitem><para> + Setting <literal>@@SQL_MODE = NULL</literal> caused an erroneous + error message. (Bug #10732) + </para></listitem> - <listitem> - <para><literal>sql_data_access</literal> column of - <literal>routines</literal> table of - <literal>INFORMATION_SCHEMA</literal> was empty. - (Bug #11055)</para> - </listitem> + <listitem><para> + Converting a <literal>VARCHAR</literal> column having an index to a + different type (such as <literal>TINYTEXT</literal>) gave rise to + an incorrect error message. (Bug #10543) + </para> - <listitem> - <para>A <literal>CAST()</literal> value could not be included in a - <literal>VIEW</literal>. (Bug #11387)</para> - </listitem> + <para> + Note that this bugfix induces a slight change in the behaviour of + indexes: If an index is defined to be the same length as a field + (or is left to default to that field's length), and the length of + the field is later changed, then the index will adopt the new + length of the field. Previously, the size of the index did not + change for some field types (such as <literal>VARCHAR</literal>) + when the field type was changed. + </para></listitem> - <listitem> - <para>Server crashed when using <literal>GROUP BY</literal> on the - result of a <literal>DIV</literal> operation on a - <literal>DATETIME</literal> value. (Bug #11385)</para> - </listitem> + <listitem><para> + <literal>sql_data_access</literal> column of + <literal>routines</literal> table of + <literal>INFORMATION_SCHEMA</literal> was empty. (Bug #11055) + </para></listitem> - <listitem> - <para>Possible <literal>NULL</literal> values in - <literal>BLOB</literal> columns could crash the server when - a <literal>BLOB</literal> was used in a - <literal>GROUP BY</literal> query. (Bug #11295)</para> - </listitem> + <listitem><para> + A <literal>CAST()</literal> value could not be included in a + <literal>VIEW</literal>. (Bug #11387) + </para></listitem> - <listitem> - <para>Fixed 64 bit compiler warning for packet length in - replication. (Bug #11064)</para> - </listitem> + <listitem><para> + Server crashed when using <literal>GROUP BY</literal> on the result + of a <literal>DIV</literal> operation on a + <literal>DATETIME</literal> value. (Bug #11385) + </para></listitem> - <listitem> - <para>Multiple range accesses in a subquery cause server crash. - (Bug #11487)</para> - </listitem> + <listitem><para> + Possible <literal>NULL</literal> values in <literal>BLOB</literal> + columns could crash the server when a <literal>BLOB</literal> was + used in a <literal>GROUP BY</literal> query. (Bug #11295) + </para></listitem> - <listitem> - <para><emphasis role="bold">Security fix</emphasis>: On Windows - systems, a user with any of the following privileges + <listitem><para> + Fixed 64 bit compiler warning for packet length in replication. + (Bug #11064) + </para></listitem> + + <listitem><para> + Multiple range accesses in a subquery cause server crash. (Bug + #11487) + </para></listitem> + + <listitem><para> + <emphasis role="bold">Security fix</emphasis>: On Windows systems, + a user with any of the following privileges <itemizedlist> - <listitem> - <para><literal>REFERENCES</literal></para> - </listitem> - - <listitem> - <para><literal>CREATE TEMPORARY TABLES</literal></para> - </listitem> - - <listitem> - <para><literal>GRANT OPTION</literal></para> - </listitem> - - <listitem> - <para><literal>CREATE</literal></para> - </listitem> - - <listitem> - <para><literal>SELECT</literal></para> - </listitem> + <listitem><para> + <literal>REFERENCES</literal> + </para></listitem> + + <listitem><para> + <literal>CREATE TEMPORARY TABLES</literal> + </para></listitem> + + <listitem><para> + <literal>GRANT OPTION</literal> + </para></listitem> + + <listitem><para> + <literal>CREATE</literal> + </para></listitem> + + <listitem><para> + <literal>SELECT</literal> + </para></listitem> </itemizedlist> @@ -501,13 +524,13 @@ <ulink url="http://cve.mitre.org/cvename.cgi?name=CAN-2005-0799">CAN-2005-0799</ulink> </para></listitem> - <listitem> - <para>An issue with index merging could cause suboptimal index - merge plans to be chosen when searching by indexes created on - <literal>DATE</literal> columns. The same issue caused the InnoDB - storage engine to issue the warning <literal>using a partial-field - key prefix in search</literal>. (Bug #8441)</para> - </listitem> + <listitem><para> + An issue with index merging could cause suboptimal index merge + plans to be chosen when searching by indexes created on + <literal>DATE</literal> columns. The same issue caused the InnoDB + storage engine to issue the warning <literal>using a partial-field + key prefix in search</literal>. (Bug #8441) + </para></listitem> <listitem><para> The <literal>mysqlhotcopy</literal> script was not parsing the @@ -777,21 +800,21 @@ <itemizedlist> - <listitem> - <para>The behaviour of the <literal>Last_query_cost</literal> - system variable has been changed. The default value is now 0 - (rather than -1) and it now has session-level scope (rather than - being global). See <xref linkend="server-status-variables"/> for - additional information.</para> - </listitem> + <listitem><para> + The behaviour of the <literal>Last_query_cost</literal> system + variable has been changed. The default value is now 0 (rather than + -1) and it now has session-level scope (rather than being global). + See <xref linkend="server-status-variables"/> for additional + information. + </para></listitem> - <listitem> - <para>All characters occuring on the same line following the - <literal>DELIMITER</literal> keyword will be set as delimiter. For - example, <literal>DELIMITER :;</literal> will set - <literal>:;</literal> as the delimiter. This behavior is now - consistent between MySQL 5.1 and MySQL 5.0. (Bug #9879)</para> - </listitem> + <listitem><para> + All characters occuring on the same line following the + <literal>DELIMITER</literal> keyword will be set as delimiter. For + example, <literal>DELIMITER :;</literal> will set + <literal>:;</literal> as the delimiter. This behavior is now + consistent between MySQL 5.1 and MySQL 5.0. (Bug #9879) + </para></listitem> <listitem><para> The <literal>table</literal>, <literal>type</literal>, and @@ -878,23 +901,23 @@ <itemizedlist> - <listitem> - <para><emphasis role="bold">Security update</emphasis>: A user - with limited privileges could obtain information about the - privileges of other users by querying objects in the - <literal>INFORMATION_SCHEMA</literal> database for which that user - did not have the requisite privileges. (Bug #10964)</para> - </listitem> + <listitem><para> + <emphasis role="bold">Security update</emphasis>: A user with + limited privileges could obtain information about the privileges of + other users by querying objects in the + <literal>INFORMATION_SCHEMA</literal> database for which that user + did not have the requisite privileges. (Bug #10964) + </para></listitem> - <listitem> - <para>Issuing a write lock for a table from one client prevented - other clients from accessing the table's metadata. For example, if - one client issued a <literal>LOCK TABLES - <replaceable>mydb</replaceable>.<replaceable>mytable</replaceable> - WRITE</literal>, then a second client attempting to execute a - <literal>USE <replaceable>mydb</replaceable>;</literal> would - hang. (Bug #9998)</para> - </listitem> + <listitem><para> + Issuing a write lock for a table from one client prevented other + clients from accessing the table's metadata. For example, if one + client issued a <literal>LOCK TABLES + <replaceable>mydb</replaceable>.<replaceable>mytable</replaceable> + WRITE</literal>, then a second client attempting to execute a + <literal>USE <replaceable>mydb</replaceable>;</literal> would hang. + (Bug #9998) + </para></listitem> <listitem><para> The <literal>LAST_DAY()</literal> failed to return @@ -4586,11 +4609,10 @@ <itemizedlist> - <listitem> - <para><literal>MEMORY</literal> tables now support indexes of up - to 500 bytes. See <xref linkend="memory-storage-engine"/>. - (Bug #10566)</para> - </listitem> + <listitem><para> + <literal>MEMORY</literal> tables now support indexes of up to 500 + bytes. See <xref linkend="memory-storage-engine"/>. (Bug #10566) + </para></listitem> <listitem><para> System variables are now treated as having @@ -4602,12 +4624,12 @@ <xref linkend="charset-collate-tricky"/>. (Bug #10904) </para></listitem> - <listitem> - <para>The statements <literal>CREATE TABLE</literal>, - <literal>TRUNCATE TABLE</literal>, <literal>DROP - DATABASE</literal>, and <literal>CREATE DATABASE</literal> cause - an implicit commit. (Bug #6883)</para> - </listitem> + <listitem><para> + The statements <literal>CREATE TABLE</literal>, <literal>TRUNCATE + TABLE</literal>, <literal>DROP DATABASE</literal>, and + <literal>CREATE DATABASE</literal> cause an implicit commit. (Bug + #6883) + </para></listitem> <listitem><para> Added the <option>--log-slow-admin-statements</option> server @@ -4668,15 +4690,29 @@ describe the issue that was fixed. Use past tense. --> <listitem><para> + <literal>NULLIF()</literal> function could produce incorrect + results if first argument is <literal>NULL</literal>. (Bug #11142) + </para></listitem> + + <listitem><para> + Optimizer performed range check when comparing unsigned integers to + negative constants, could cause errors. (Bug #11185) + </para></listitem> + + <listitem><para> + Cluster failed to build with GCC 4.0. (Bug #11377) + </para></listitem> + + <listitem><para> The <literal>LAST_DAY()</literal> failed to return <literal>NULL</literal> when supplied with an invalid argument. See <xref linkend="date-and-time-functions"/>. (Bug #10568) </para></listitem> - <listitem> - <para>Setting <literal>@@SQL_MODE = NULL</literal> caused an - erroneous error message. (Bug #10732)</para> - </listitem> + <listitem><para> + Setting <literal>@@SQL_MODE = NULL</literal> caused an erroneous + error message. (Bug #10732) + </para></listitem> <listitem> <para>Setting <literal>@@SQL_MODE = NULL</literal> caused an --- 1.4/refman-5.0/functions.xml 2005-06-23 16:01:06 -06:00 +++ 1.5/refman-5.0/functions.xml 2005-06-24 11:41:10 -06:00 @@ -1028,7 +1028,13 @@ <literal>=</literal> is always false. </para> - <para>The <literal>ISNULL()</literal> function shares some special behaviors with the <literal>IS NULL</literal> comparison operator, see the description of <literal>IS NULL</literal> at <xref linkend="comparison-operators" />.</para> + <para> + The <literal>ISNULL()</literal> function shares some special + behaviors with the <literal>IS NULL</literal> comparison operator, + see the description of <literal>IS NULL</literal> at + <xref linkend="comparison-operators" />. + </para> + <para> <!-- description_for_help_topic INTERVAL --> </para> @@ -10354,6 +10360,10 @@ </para></listitem> <listitem><para> + <literal>DECIMAL</literal> + </para></listitem> + + <listitem><para> <literal>SIGNED [INTEGER]</literal> </para></listitem> @@ -10379,6 +10389,10 @@ available as of MySQL 4.0.2. The <literal>CHAR</literal> conversion type is available as of 4.0.6. The <literal>USING</literal> form of <literal>CONVERT()</literal> is available as of 4.1.0. + </para> + + <para> + The <literal>DECIMAL</literal> type is available as of MySQL 5.0.8. </para> <para> --- 1.29/refman-5.0/news.xml 2005-06-24 07:59:29 -06:00 +++ 1.30/refman-5.0/news.xml 2005-06-24 11:41:10 -06:00 @@ -206,32 +206,48 @@ </para> <section id="news-5-0-9"> - <title id="title-news-5-0-9">&title-news-5-0-9;</title> - <para> - Functionality added or changed: - </para> + <title id="title-news-5-0-9">&title-news-5-0-9;</title> - <itemizedlist> + <para> + Functionality added or changed: + </para> - <listitem> - <para></para> - </listitem> + <itemizedlist> - </itemizedlist> + <listitem><para></para></listitem> - <para> - Bugs fixed: - </para> + </itemizedlist> - <itemizedlist> + <para> + Bugs fixed: + </para> - <listitem> - <para>Clients would hang following some errors with stored - procedures. (Bug #9503)</para> - </listitem> + <itemizedlist> - </itemizedlist> + <listitem><para> + Optimizer performed range check when comparing unsigned integers to + negative constants, could cause errors. (Bug #11185) + </para></listitem> + + <listitem><para> + Wrong comparison method used in <literal>VIEW</literal> when + relaxed date syntax used (i.e. <literal>2005.06.10</literal>). (Bug + #11325) + </para></listitem> + + <listitem><para> + The <literal>ENCRYPT()</literal> and + <literal>SUBSTRING_INDEX()</literal> functions would cause errors + when used with a <literal>VIEW</literal>. (Bug #7024) + </para></listitem> + + <listitem><para> + Clients would hang following some errors with stored procedures. + (Bug #9503) + </para></listitem> + + </itemizedlist> </section> @@ -258,11 +274,10 @@ <itemizedlist> - <listitem> - <para><literal>MEMORY</literal> tables now support indexes of up - to 500 bytes. See <xref linkend="memory-storage-engine"/>. - (Bug #10566)</para> - </listitem> + <listitem><para> + <literal>MEMORY</literal> tables now support indexes of up to 500 + bytes. See <xref linkend="memory-storage-engine"/>. (Bug #10566) + </para></listitem> <listitem><para> New <literal>SQL_MODE</literal> - @@ -271,12 +286,12 @@ disabled or not compiled in. (Bug #6877) </para></listitem> - <listitem> - <para>The statements <literal>CREATE TABLE</literal>, - <literal>TRUNCATE TABLE</literal>, <literal>DROP - DATABASE</literal>, and <literal>CREATE DATABASE</literal> cause - an implicit commit. (Bug #6883)</para> - </listitem> + <listitem><para> + The statements <literal>CREATE TABLE</literal>, <literal>TRUNCATE + TABLE</literal>, <literal>DROP DATABASE</literal>, and + <literal>CREATE DATABASE</literal> cause an implicit commit. (Bug + #6883) + </para></listitem> <listitem><para> Expanded on information provided in general log and slow query log @@ -405,87 +420,95 @@ Thanks! --> + <listitem><para> + <literal>CAST( ... AS DECIMAL) didn't work for strings. (Bug + #11283)</literal> + </para></listitem> - <listitem> - <para>Setting <literal>@@SQL_MODE = NULL</literal> caused an - erroneous error message. (Bug #10732)</para> - </listitem> + <listitem><para> + <literal>NULLIF()</literal> function could produce incorrect + results if first argument is <literal>NULL</literal>. (Bug #11142) + </para></listitem> - <listitem> - <para>Converting a <literal>VARCHAR</literal> column having an - index to a different type (such as <literal>TINYTEXT</literal>) - gave rise to an incorrect error message. (Bug #10543)</para> - - <para>Note that this bugfix induces a slight change in the - behaviour of indexes: If an index is defined to be the same length - as a field (or is left to default to that field's length), and the - length of the field is later changed, then the index will adopt - the new length of the field. Previously, the size of the index did - not change for some field types (such as - <literal>VARCHAR</literal>) when the field type was - changed.</para> - </listitem> + <listitem><para> + Setting <literal>@@SQL_MODE = NULL</literal> caused an erroneous + error message. (Bug #10732) + </para></listitem> - <listitem> - <para><literal>sql_data_access</literal> column of - <literal>routines</literal> table of - <literal>INFORMATION_SCHEMA</literal> was empty. - (Bug #11055)</para> - </listitem> + <listitem><para> + Converting a <literal>VARCHAR</literal> column having an index to a + different type (such as <literal>TINYTEXT</literal>) gave rise to + an incorrect error message. (Bug #10543) + </para> - <listitem> - <para>A <literal>CAST()</literal> value could not be included in a - <literal>VIEW</literal>. (Bug #11387)</para> - </listitem> + <para> + Note that this bugfix induces a slight change in the behaviour of + indexes: If an index is defined to be the same length as a field + (or is left to default to that field's length), and the length of + the field is later changed, then the index will adopt the new + length of the field. Previously, the size of the index did not + change for some field types (such as <literal>VARCHAR</literal>) + when the field type was changed. + </para></listitem> - <listitem> - <para>Server crashed when using <literal>GROUP BY</literal> on the - result of a <literal>DIV</literal> operation on a - <literal>DATETIME</literal> value. (Bug #11385)</para> - </listitem> + <listitem><para> + <literal>sql_data_access</literal> column of + <literal>routines</literal> table of + <literal>INFORMATION_SCHEMA</literal> was empty. (Bug #11055) + </para></listitem> - <listitem> - <para>Possible <literal>NULL</literal> values in - <literal>BLOB</literal> columns could crash the server when - a <literal>BLOB</literal> was used in a - <literal>GROUP BY</literal> query. (Bug #11295)</para> - </listitem> + <listitem><para> + A <literal>CAST()</literal> value could not be included in a + <literal>VIEW</literal>. (Bug #11387) + </para></listitem> - <listitem> - <para>Fixed 64 bit compiler warning for packet length in - replication. (Bug #11064)</para> - </listitem> + <listitem><para> + Server crashed when using <literal>GROUP BY</literal> on the result + of a <literal>DIV</literal> operation on a + <literal>DATETIME</literal> value. (Bug #11385) + </para></listitem> - <listitem> - <para>Multiple range accesses in a subquery cause server crash. - (Bug #11487)</para> - </listitem> + <listitem><para> + Possible <literal>NULL</literal> values in <literal>BLOB</literal> + columns could crash the server when a <literal>BLOB</literal> was + used in a <literal>GROUP BY</literal> query. (Bug #11295) + </para></listitem> - <listitem> - <para><emphasis role="bold">Security fix</emphasis>: On Windows - systems, a user with any of the following privileges + <listitem><para> + Fixed 64 bit compiler warning for packet length in replication. + (Bug #11064) + </para></listitem> + + <listitem><para> + Multiple range accesses in a subquery cause server crash. (Bug + #11487) + </para></listitem> + + <listitem><para> + <emphasis role="bold">Security fix</emphasis>: On Windows systems, + a user with any of the following privileges <itemizedlist> - <listitem> - <para><literal>REFERENCES</literal></para> - </listitem> - - <listitem> - <para><literal>CREATE TEMPORARY TABLES</literal></para> - </listitem> - - <listitem> - <para><literal>GRANT OPTION</literal></para> - </listitem> - - <listitem> - <para><literal>CREATE</literal></para> - </listitem> - - <listitem> - <para><literal>SELECT</literal></para> - </listitem> + <listitem><para> + <literal>REFERENCES</literal> + </para></listitem> + + <listitem><para> + <literal>CREATE TEMPORARY TABLES</literal> + </para></listitem> + + <listitem><para> + <literal>GRANT OPTION</literal> + </para></listitem> + + <listitem><para> + <literal>CREATE</literal> + </para></listitem> + + <listitem><para> + <literal>SELECT</literal> + </para></listitem> </itemizedlist> @@ -501,13 +524,13 @@ <ulink url="http://cve.mitre.org/cvename.cgi?name=CAN-2005-0799">CAN-2005-0799</ulink> </para></listitem> - <listitem> - <para>An issue with index merging could cause suboptimal index - merge plans to be chosen when searching by indexes created on - <literal>DATE</literal> columns. The same issue caused the InnoDB - storage engine to issue the warning <literal>using a partial-field - key prefix in search</literal>. (Bug #8441)</para> - </listitem> + <listitem><para> + An issue with index merging could cause suboptimal index merge + plans to be chosen when searching by indexes created on + <literal>DATE</literal> columns. The same issue caused the InnoDB + storage engine to issue the warning <literal>using a partial-field + key prefix in search</literal>. (Bug #8441) + </para></listitem> <listitem><para> The <literal>mysqlhotcopy</literal> script was not parsing the @@ -777,21 +800,21 @@ <itemizedlist> - <listitem> - <para>The behaviour of the <literal>Last_query_cost</literal> - system variable has been changed. The default value is now 0 - (rather than -1) and it now has session-level scope (rather than - being global). See <xref linkend="server-status-variables"/> for - additional information.</para> - </listitem> + <listitem><para> + The behaviour of the <literal>Last_query_cost</literal> system + variable has been changed. The default value is now 0 (rather than + -1) and it now has session-level scope (rather than being global). + See <xref linkend="server-status-variables"/> for additional + information. + </para></listitem> - <listitem> - <para>All characters occuring on the same line following the - <literal>DELIMITER</literal> keyword will be set as delimiter. For - example, <literal>DELIMITER :;</literal> will set - <literal>:;</literal> as the delimiter. This behavior is now - consistent between MySQL 5.1 and MySQL 5.0. (Bug #9879)</para> - </listitem> + <listitem><para> + All characters occuring on the same line following the + <literal>DELIMITER</literal> keyword will be set as delimiter. For + example, <literal>DELIMITER :;</literal> will set + <literal>:;</literal> as the delimiter. This behavior is now + consistent between MySQL 5.1 and MySQL 5.0. (Bug #9879) + </para></listitem> <listitem><para> The <literal>table</literal>, <literal>type</literal>, and @@ -878,23 +901,23 @@ <itemizedlist> - <listitem> - <para><emphasis role="bold">Security update</emphasis>: A user - with limited privileges could obtain information about the - privileges of other users by querying objects in the - <literal>INFORMATION_SCHEMA</literal> database for which that user - did not have the requisite privileges. (Bug #10964)</para> - </listitem> + <listitem><para> + <emphasis role="bold">Security update</emphasis>: A user with + limited privileges could obtain information about the privileges of + other users by querying objects in the + <literal>INFORMATION_SCHEMA</literal> database for which that user + did not have the requisite privileges. (Bug #10964) + </para></listitem> - <listitem> - <para>Issuing a write lock for a table from one client prevented - other clients from accessing the table's metadata. For example, if - one client issued a <literal>LOCK TABLES - <replaceable>mydb</replaceable>.<replaceable>mytable</replaceable> - WRITE</literal>, then a second client attempting to execute a - <literal>USE <replaceable>mydb</replaceable>;</literal> would - hang. (Bug #9998)</para> - </listitem> + <listitem><para> + Issuing a write lock for a table from one client prevented other + clients from accessing the table's metadata. For example, if one + client issued a <literal>LOCK TABLES + <replaceable>mydb</replaceable>.<replaceable>mytable</replaceable> + WRITE</literal>, then a second client attempting to execute a + <literal>USE <replaceable>mydb</replaceable>;</literal> would hang. + (Bug #9998) + </para></listitem> <listitem><para> The <literal>LAST_DAY()</literal> failed to return @@ -4586,11 +4609,10 @@ <itemizedlist> - <listitem> - <para><literal>MEMORY</literal> tables now support indexes of up - to 500 bytes. See <xref linkend="memory-storage-engine"/>. - (Bug #10566)</para> - </listitem> + <listitem><para> + <literal>MEMORY</literal> tables now support indexes of up to 500 + bytes. See <xref linkend="memory-storage-engine"/>. (Bug #10566) + </para></listitem> <listitem><para> System variables are now treated as having @@ -4602,12 +4624,12 @@ <xref linkend="charset-collate-tricky"/>. (Bug #10904) </para></listitem> - <listitem> - <para>The statements <literal>CREATE TABLE</literal>, - <literal>TRUNCATE TABLE</literal>, <literal>DROP - DATABASE</literal>, and <literal>CREATE DATABASE</literal> cause - an implicit commit. (Bug #6883)</para> - </listitem> + <listitem><para> + The statements <literal>CREATE TABLE</literal>, <literal>TRUNCATE + TABLE</literal>, <literal>DROP DATABASE</literal>, and + <literal>CREATE DATABASE</literal> cause an implicit commit. (Bug + #6883) + </para></listitem> <listitem><para> Added the <option>--log-slow-admin-statements</option> server @@ -4668,15 +4690,29 @@ describe the issue that was fixed. Use past tense. --> <listitem><para> + <literal>NULLIF()</literal> function could produce incorrect + results if first argument is <literal>NULL</literal>. (Bug #11142) + </para></listitem> + + <listitem><para> + Optimizer performed range check when comparing unsigned integers to + negative constants, could cause errors. (Bug #11185) + </para></listitem> + + <listitem><para> + Cluster failed to build with GCC 4.0. (Bug #11377) + </para></listitem> + + <listitem><para> The <literal>LAST_DAY()</literal> failed to return <literal>NULL</literal> when supplied with an invalid argument. See <xref linkend="date-and-time-functions"/>. (Bug #10568) </para></listitem> - <listitem> - <para>Setting <literal>@@SQL_MODE = NULL</literal> caused an - erroneous error message. (Bug #10732)</para> - </listitem> + <listitem><para> + Setting <literal>@@SQL_MODE = NULL</literal> caused an erroneous + error message. (Bug #10732) + </para></listitem> <listitem> <para>Setting <literal>@@SQL_MODE = NULL</literal> caused an --- 1.4/refman/functions.xml 2005-06-23 16:01:06 -06:00 +++ 1.5/refman/functions.xml 2005-06-24 11:41:10 -06:00 @@ -1028,7 +1028,13 @@ <literal>=</literal> is always false. </para> - <para>The <literal>ISNULL()</literal> function shares some special behaviors with the <literal>IS NULL</literal> comparison operator, see the description of <literal>IS NULL</literal> at <xref linkend="comparison-operators" />.</para> + <para> + The <literal>ISNULL()</literal> function shares some special + behaviors with the <literal>IS NULL</literal> comparison operator, + see the description of <literal>IS NULL</literal> at + <xref linkend="comparison-operators" />. + </para> + <para> <!-- description_for_help_topic INTERVAL --> </para> @@ -10354,6 +10360,10 @@ </para></listitem> <listitem><para> + <literal>DECIMAL</literal> + </para></listitem> + + <listitem><para> <literal>SIGNED [INTEGER]</literal> </para></listitem> @@ -10379,6 +10389,10 @@ available as of MySQL 4.0.2. The <literal>CHAR</literal> conversion type is available as of 4.0.6. The <literal>USING</literal> form of <literal>CONVERT()</literal> is available as of 4.1.0. + </para> + + <para> + The <literal>DECIMAL</literal> type is available as of MySQL 5.0.8. </para> <para> --- 1.34/refman/news.xml 2005-06-24 07:59:30 -06:00 +++ 1.35/refman/news.xml 2005-06-24 11:41:11 -06:00 @@ -206,32 +206,48 @@ </para> <section id="news-5-0-9"> - <title id="title-news-5-0-9">&title-news-5-0-9;</title> - <para> - Functionality added or changed: - </para> + <title id="title-news-5-0-9">&title-news-5-0-9;</title> - <itemizedlist> + <para> + Functionality added or changed: + </para> - <listitem> - <para></para> - </listitem> + <itemizedlist> - </itemizedlist> + <listitem><para></para></listitem> - <para> - Bugs fixed: - </para> + </itemizedlist> - <itemizedlist> + <para> + Bugs fixed: + </para> - <listitem> - <para>Clients would hang following some errors with stored - procedures. (Bug #9503)</para> - </listitem> + <itemizedlist> - </itemizedlist> + <listitem><para> + Optimizer performed range check when comparing unsigned integers to + negative constants, could cause errors. (Bug #11185) + </para></listitem> + + <listitem><para> + Wrong comparison method used in <literal>VIEW</literal> when + relaxed date syntax used (i.e. <literal>2005.06.10</literal>). (Bug + #11325) + </para></listitem> + + <listitem><para> + The <literal>ENCRYPT()</literal> and + <literal>SUBSTRING_INDEX()</literal> functions would cause errors + when used with a <literal>VIEW</literal>. (Bug #7024) + </para></listitem> + + <listitem><para> + Clients would hang following some errors with stored procedures. + (Bug #9503) + </para></listitem> + + </itemizedlist> </section> @@ -258,11 +274,10 @@ <itemizedlist> - <listitem> - <para><literal>MEMORY</literal> tables now support indexes of up - to 500 bytes. See <xref linkend="memory-storage-engine"/>. - (Bug #10566)</para> - </listitem> + <listitem><para> + <literal>MEMORY</literal> tables now support indexes of up to 500 + bytes. See <xref linkend="memory-storage-engine"/>. (Bug #10566) + </para></listitem> <listitem><para> New <literal>SQL_MODE</literal> - @@ -271,12 +286,12 @@ disabled or not compiled in. (Bug #6877) </para></listitem> - <listitem> - <para>The statements <literal>CREATE TABLE</literal>, - <literal>TRUNCATE TABLE</literal>, <literal>DROP - DATABASE</literal>, and <literal>CREATE DATABASE</literal> cause - an implicit commit. (Bug #6883)</para> - </listitem> + <listitem><para> + The statements <literal>CREATE TABLE</literal>, <literal>TRUNCATE + TABLE</literal>, <literal>DROP DATABASE</literal>, and + <literal>CREATE DATABASE</literal> cause an implicit commit. (Bug + #6883) + </para></listitem> <listitem><para> Expanded on information provided in general log and slow query log @@ -405,87 +420,95 @@ Thanks! --> + <listitem><para> + <literal>CAST( ... AS DECIMAL) didn't work for strings. (Bug + #11283)</literal> + </para></listitem> - <listitem> - <para>Setting <literal>@@SQL_MODE = NULL</literal> caused an - erroneous error message. (Bug #10732)</para> - </listitem> + <listitem><para> + <literal>NULLIF()</literal> function could produce incorrect + results if first argument is <literal>NULL</literal>. (Bug #11142) + </para></listitem> - <listitem> - <para>Converting a <literal>VARCHAR</literal> column having an - index to a different type (such as <literal>TINYTEXT</literal>) - gave rise to an incorrect error message. (Bug #10543)</para> - - <para>Note that this bugfix induces a slight change in the - behaviour of indexes: If an index is defined to be the same length - as a field (or is left to default to that field's length), and the - length of the field is later changed, then the index will adopt - the new length of the field. Previously, the size of the index did - not change for some field types (such as - <literal>VARCHAR</literal>) when the field type was - changed.</para> - </listitem> + <listitem><para> + Setting <literal>@@SQL_MODE = NULL</literal> caused an erroneous + error message. (Bug #10732) + </para></listitem> - <listitem> - <para><literal>sql_data_access</literal> column of - <literal>routines</literal> table of - <literal>INFORMATION_SCHEMA</literal> was empty. - (Bug #11055)</para> - </listitem> + <listitem><para> + Converting a <literal>VARCHAR</literal> column having an index to a + different type (such as <literal>TINYTEXT</literal>) gave rise to + an incorrect error message. (Bug #10543) + </para> - <listitem> - <para>A <literal>CAST()</literal> value could not be included in a - <literal>VIEW</literal>. (Bug #11387)</para> - </listitem> + <para> + Note that this bugfix induces a slight change in the behaviour of + indexes: If an index is defined to be the same length as a field + (or is left to default to that field's length), and the length of + the field is later changed, then the index will adopt the new + length of the field. Previously, the size of the index did not + change for some field types (such as <literal>VARCHAR</literal>) + when the field type was changed. + </para></listitem> - <listitem> - <para>Server crashed when using <literal>GROUP BY</literal> on the - result of a <literal>DIV</literal> operation on a - <literal>DATETIME</literal> value. (Bug #11385)</para> - </listitem> + <listitem><para> + <literal>sql_data_access</literal> column of + <literal>routines</literal> table of + <literal>INFORMATION_SCHEMA</literal> was empty. (Bug #11055) + </para></listitem> - <listitem> - <para>Possible <literal>NULL</literal> values in - <literal>BLOB</literal> columns could crash the server when - a <literal>BLOB</literal> was used in a - <literal>GROUP BY</literal> query. (Bug #11295)</para> - </listitem> + <listitem><para> + A <literal>CAST()</literal> value could not be included in a + <literal>VIEW</literal>. (Bug #11387) + </para></listitem> - <listitem> - <para>Fixed 64 bit compiler warning for packet length in - replication. (Bug #11064)</para> - </listitem> + <listitem><para> + Server crashed when using <literal>GROUP BY</literal> on the result + of a <literal>DIV</literal> operation on a + <literal>DATETIME</literal> value. (Bug #11385) + </para></listitem> - <listitem> - <para>Multiple range accesses in a subquery cause server crash. - (Bug #11487)</para> - </listitem> + <listitem><para> + Possible <literal>NULL</literal> values in <literal>BLOB</literal> + columns could crash the server when a <literal>BLOB</literal> was + used in a <literal>GROUP BY</literal> query. (Bug #11295) + </para></listitem> - <listitem> - <para><emphasis role="bold">Security fix</emphasis>: On Windows - systems, a user with any of the following privileges + <listitem><para> + Fixed 64 bit compiler warning for packet length in replication. + (Bug #11064) + </para></listitem> + + <listitem><para> + Multiple range accesses in a subquery cause server crash. (Bug + #11487) + </para></listitem> + + <listitem><para> + <emphasis role="bold">Security fix</emphasis>: On Windows systems, + a user with any of the following privileges <itemizedlist> - <listitem> - <para><literal>REFERENCES</literal></para> - </listitem> - - <listitem> - <para><literal>CREATE TEMPORARY TABLES</literal></para> - </listitem> - - <listitem> - <para><literal>GRANT OPTION</literal></para> - </listitem> - - <listitem> - <para><literal>CREATE</literal></para> - </listitem> - - <listitem> - <para><literal>SELECT</literal></para> - </listitem> + <listitem><para> + <literal>REFERENCES</literal> + </para></listitem> + + <listitem><para> + <literal>CREATE TEMPORARY TABLES</literal> + </para></listitem> + + <listitem><para> + <literal>GRANT OPTION</literal> + </para></listitem> + + <listitem><para> + <literal>CREATE</literal> + </para></listitem> + + <listitem><para> + <literal>SELECT</literal> + </para></listitem> </itemizedlist> @@ -501,13 +524,13 @@ <ulink url="http://cve.mitre.org/cvename.cgi?name=CAN-2005-0799">CAN-2005-0799</ulink> </para></listitem> - <listitem> - <para>An issue with index merging could cause suboptimal index - merge plans to be chosen when searching by indexes created on - <literal>DATE</literal> columns. The same issue caused the InnoDB - storage engine to issue the warning <literal>using a partial-field - key prefix in search</literal>. (Bug #8441)</para> - </listitem> + <listitem><para> + An issue with index merging could cause suboptimal index merge + plans to be chosen when searching by indexes created on + <literal>DATE</literal> columns. The same issue caused the InnoDB + storage engine to issue the warning <literal>using a partial-field + key prefix in search</literal>. (Bug #8441) + </para></listitem> <listitem><para> The <literal>mysqlhotcopy</literal> script was not parsing the @@ -777,21 +800,21 @@ <itemizedlist> - <listitem> - <para>The behaviour of the <literal>Last_query_cost</literal> - system variable has been changed. The default value is now 0 - (rather than -1) and it now has session-level scope (rather than - being global). See <xref linkend="server-status-variables"/> for - additional information.</para> - </listitem> + <listitem><para> + The behaviour of the <literal>Last_query_cost</literal> system + variable has been changed. The default value is now 0 (rather than + -1) and it now has session-level scope (rather than being global). + See <xref linkend="server-status-variables"/> for additional + information. + </para></listitem> - <listitem> - <para>All characters occuring on the same line following the - <literal>DELIMITER</literal> keyword will be set as delimiter. For - example, <literal>DELIMITER :;</literal> will set - <literal>:;</literal> as the delimiter. This behavior is now - consistent between MySQL 5.1 and MySQL 5.0. (Bug #9879)</para> - </listitem> + <listitem><para> + All characters occuring on the same line following the + <literal>DELIMITER</literal> keyword will be set as delimiter. For + example, <literal>DELIMITER :;</literal> will set + <literal>:;</literal> as the delimiter. This behavior is now + consistent between MySQL 5.1 and MySQL 5.0. (Bug #9879) + </para></listitem> <listitem><para> The <literal>table</literal>, <literal>type</literal>, and @@ -860,23 +883,23 @@ <itemizedlist> - <listitem> - <para><emphasis role="bold">Security update</emphasis>: A user - with limited privileges could obtain information about the - privileges of other users by querying objects in the - <literal>INFORMATION_SCHEMA</literal> database for which that user - did not have the requisite privileges. (Bug #10964)</para> - </listitem> + <listitem><para> + <emphasis role="bold">Security update</emphasis>: A user with + limited privileges could obtain information about the privileges of + other users by querying objects in the + <literal>INFORMATION_SCHEMA</literal> database for which that user + did not have the requisite privileges. (Bug #10964) + </para></listitem> - <listitem> - <para>Issuing a write lock for a table from one client prevented - other clients from accessing the table's metadata. For example, if - one client issued a <literal>LOCK TABLES - <replaceable>mydb</replaceable>.<replaceable>mytable</replaceable> - WRITE</literal>, then a second client attempting to execute a - <literal>USE <replaceable>mydb</replaceable>;</literal> would - hang. (Bug #9998)</para> - </listitem> + <listitem><para> + Issuing a write lock for a table from one client prevented other + clients from accessing the table's metadata. For example, if one + client issued a <literal>LOCK TABLES + <replaceable>mydb</replaceable>.<replaceable>mytable</replaceable> + WRITE</literal>, then a second client attempting to execute a + <literal>USE <replaceable>mydb</replaceable>;</literal> would hang. + (Bug #9998) + </para></listitem> <listitem><para> The <literal>LAST_DAY()</literal> failed to return @@ -4568,11 +4591,10 @@ <itemizedlist> - <listitem> - <para><literal>MEMORY</literal> tables now support indexes of up - to 500 bytes. See <xref linkend="memory-storage-engine"/>. - (Bug #10566)</para> - </listitem> + <listitem><para> + <literal>MEMORY</literal> tables now support indexes of up to 500 + bytes. See <xref linkend="memory-storage-engine"/>. (Bug #10566) + </para></listitem> <listitem><para> System variables are now treated as having @@ -4584,12 +4606,12 @@ <xref linkend="charset-collate-tricky"/>. (Bug #10904) </para></listitem> - <listitem> - <para>The statements <literal>CREATE TABLE</literal>, - <literal>TRUNCATE TABLE</literal>, <literal>DROP - DATABASE</literal>, and <literal>CREATE DATABASE</literal> cause - an implicit commit. (Bug #6883)</para> - </listitem> + <listitem><para> + The statements <literal>CREATE TABLE</literal>, <literal>TRUNCATE + TABLE</literal>, <literal>DROP DATABASE</literal>, and + <literal>CREATE DATABASE</literal> cause an implicit commit. (Bug + #6883) + </para></listitem> <listitem><para> Added the <option>--log-slow-admin-statements</option> server @@ -4650,15 +4672,29 @@ describe the issue that was fixed. Use past tense. --> <listitem><para> + <literal>NULLIF()</literal> function could produce incorrect + results if first argument is <literal>NULL</literal>. (Bug #11142) + </para></listitem> + + <listitem><para> + Optimizer performed range check when comparing unsigned integers to + negative constants, could cause errors. (Bug #11185) + </para></listitem> + + <listitem><para> + Cluster failed to build with GCC 4.0. (Bug #11377) + </para></listitem> + + <listitem><para> The <literal>LAST_DAY()</literal> failed to return <literal>NULL</literal> when supplied with an invalid argument. See <xref linkend="date-and-time-functions"/>. (Bug #10568) </para></listitem> - <listitem> - <para>Setting <literal>@@SQL_MODE = NULL</literal> caused an - erroneous error message. (Bug #10732)</para> - </listitem> + <listitem><para> + Setting <literal>@@SQL_MODE = NULL</literal> caused an erroneous + error message. (Bug #10732) + </para></listitem> <listitem><para> Server crashed when using <literal>GROUP BY</literal> on the result
| Thread | ||
|---|---|---|
| • bk commit - mysqldoc@docsrva tree (Mike.Hillyer:1.2883) | mhillyer | 24 Jun |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 0.877 sec. using MySQL 5.1.14-beta-log