| List: | Internals | « Previous MessageNext Message » | |
| From: | paul | Date: | September 14 2005 3:08am |
| Subject: | bk commit - mysqldoc@docsrva tree (paul:1.3554) | ||
| View as plain text | |||
Below is the list of changes that have just been committed into a local mysqldoc repository of paul. When paul 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.3554 05/09/13 20:08:47 paul@stripped +2 -0 news-4.1.xml, news-5.0.xml: Document bugfix. (Bug #12517) news-5.0.xml: Document bugfix. (Bug #12993) Document bugfix. (Bug #11775) news-4.1.xml: Document bugfix. (Bug #6008) news-5.0.xml: Document bugfix. (Bug #6808) Document bugfix. (Bug #12891) Document bugfix. (Bug #12938) Document bugfix. (Bug #12917) Document bugfix. (Bug #13067) Document bugfix. (Bug #13133) refman-common/news-4.1.xml 1.93 05/09/13 20:02:47 paul@stripped +8 -0 Document bugfix. (Bug #12517) refman-common/news-5.0.xml 1.180 05/09/13 20:02:44 paul@stripped +8 -0 Document bugfix. (Bug #12517) refman-common/news-5.0.xml 1.179 05/09/13 19:51:10 paul@stripped +8 -0 Document bugfix. (Bug #12993) refman-common/news-5.0.xml 1.178 05/09/13 19:45:46 paul@stripped +8 -0 Document bugfix. (Bug #11775) refman-common/news-4.1.xml 1.92 05/09/13 19:43:49 paul@stripped +16 -6 Document bugfix. (Bug #6008) refman-common/news-5.0.xml 1.177 05/09/13 19:43:00 paul@stripped +11 -0 Document bugfix. (Bug #6808) refman-common/news-5.0.xml 1.176 05/09/13 19:33:00 paul@stripped +7 -0 Document bugfix. (Bug #12891) refman-common/news-5.0.xml 1.175 05/09/13 19:29:06 paul@stripped +8 -0 Document bugfix. (Bug #12938) refman-common/news-5.0.xml 1.174 05/09/13 19:25:44 paul@stripped +8 -0 Document bugfix. (Bug #12917) refman-common/news-5.0.xml 1.173 05/09/13 19:23:31 paul@stripped +8 -0 Document bugfix. (Bug #13067) refman-common/news-5.0.xml 1.172 05/09/13 19:19:29 paul@stripped +11 -4 Document bugfix. (Bug #13133) # 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: paul # Host: frost.snake.net # Root: /Users/paul/bk/mysqldoc --- 1.91/refman-common/news-4.1.xml 2005-09-13 18:06:51 -05:00 +++ 1.93/refman-common/news-4.1.xml 2005-09-13 20:02:47 -05:00 @@ -169,6 +169,15 @@ <listitem> <para> + When using <literal>IF NOT EXISTS</literal> with + <literal>CREATE DATABASE</literal> or <literal>CREATE + TABLE</literal>, a warning now is generated if the database or + table already exists. (Bug #6008): + </para> + </listitem> + + <listitem> + <para> A new command line argument was added to mysqld to ignore client character set information sent during handshake, and use server side settings instead, to reproduce 4.0 behaviour @@ -193,6 +202,14 @@ <listitem> <para> + A client connection thread cleanup problem caused the server + to crash when closing the connection if the binary log was + enabled. (Bug #12517) + </para> + </listitem> + + <listitem> + <para> <literal>CHECKSUM TABLE</literal> command returned <literal>0</literal> for tables with deleted rows. After upgrading, users who used stored checksum information to @@ -2157,10 +2174,11 @@ and isolation level of the transaction is not set to serializable then <literal>InnoDB</literal> uses a consistent read for select in clauses like <literal>INSERT - INTO…SELECT</literal> and <literal>UPDATE…(SELECT)</literal> - that do not specify <literal>FOR UPDATE</literal> or - <literal>IN SHARE MODE</literal>. Thus no locks are set to - rows read from selected table. + INTO…SELECT</literal> and + <literal>UPDATE…(SELECT)</literal> that do not specify + <literal>FOR UPDATE</literal> or <literal>IN SHARE + MODE</literal>. Thus no locks are set to rows read from + selected table. </para> </listitem> @@ -3950,8 +3968,8 @@ <listitem> <para> InnoDB: Relaxed locking in <literal>INSERT…SELECT</literal>, - single table <literal>UPDATE…SELECT</literal> and single table - <literal>DELETE…SELECT</literal> clauses when + single table <literal>UPDATE…SELECT</literal> and single + table <literal>DELETE…SELECT</literal> clauses when <literal>innodb_locks_unsafe_for_binlog</literal> is used and isolation level of the transaction is not serializable. <literal>InnoDB</literal> uses consistent read in these cases --- 1.171/refman-common/news-5.0.xml 2005-09-13 18:06:51 -05:00 +++ 1.180/refman-common/news-5.0.xml 2005-09-13 20:02:44 -05:00 @@ -243,6 +243,79 @@ <listitem> <para> + A client connection thread cleanup problem caused the server + to crash when closing the connection if the binary log was + enabled. (Bug #12517) + </para> + </listitem> + + <listitem> + <para> + Using <literal>AS</literal> to rename a column selected from a + view in a subquery made it not possible to refer to that + column in the outer query. (Bug #12993) + </para> + </listitem> + + <listitem> + <para> + The <literal>character_set_system</literal> system variable + could not be selected with <literal>SELECT + @@character_set_system</literal>. (Bug #11775) + </para> + </listitem> + + <listitem> + <para> + A view-creation statement of the form <literal>CREATE VIEW + <replaceable>name</replaceable> AS SELECT ... FROM + <replaceable>tbl_name</replaceable> AS + <replaceable>name</replaceable></literal> failed with a + <literal>Not unique table/alias: + '<replaceable>name</replaceable>'</literal> error. (Bug #6808) + </para> + </listitem> + + <listitem> + <para> + <literal>UNION [DISTINCT]</literal> was not removing all + duplicates for multi-byte character values. (Bug #12891) + </para> + </listitem> + + <listitem> + <para> + Multiplying a <literal>DECIMAL</literal> value within a loop + in a stored routine could incorrectly result in a value of + <literal>NULL</literal>. (Bug #12938) + </para> + </listitem> + + <listitem> + <para> + <command>mysql</command> and <command>mysqldump</command> were + ignoring the <option>--defaults-extra-file</option> option. + (Bug #12917) + </para> + </listitem> + + <listitem> + <para> + Columns named in the <literal>USING()</literal> clause of + <literal>JOIN ... USING()</literal> were incorrectly resolved + in case-sensitive fashion. (Bug #13067) + </para> + </listitem> + + <listitem> + <para> + Local variables in stored routines were not always initialized + correctly. (Bug #13133) + </para> + </listitem> + + <listitem> + <para> <literal>SHOW FIELDS FROM <replaceable>schemaname</replaceable>.<replaceable>viewname</replaceable></literal> caused error 1046 when no default schema was set. (Bug #12905) @@ -5400,8 +5473,8 @@ InnoDB: True <literal>VARCHAR</literal>: InnoDB stored the 'position' of a row wrong in a column prefix primary key index; this could cause MySQL to complain <literal>ERROR 1032: - Can't find record …</literal> in an update of the primary key, - and also some <literal>ORDER BY</literal> or + Can't find record …</literal> in an update of the primary + key, and also some <literal>ORDER BY</literal> or <literal>DISTINCT</literal> queries. (Bug #9314) </para> </listitem> @@ -6303,8 +6376,8 @@ <listitem> <para> InnoDB: Relaxed locking in <literal>INSERT…SELECT</literal>, - single table <literal>UPDATE…SELECT</literal> and single table - <literal>DELETE…SELECT</literal> clauses when + single table <literal>UPDATE…SELECT</literal> and single + table <literal>DELETE…SELECT</literal> clauses when <literal>innodb_locks_unsafe_for_binlog</literal> is used and isolation level of the transaction is not serializable. <literal>InnoDB</literal> uses consistent read in these cases
| Thread | ||
|---|---|---|
| • bk commit - mysqldoc@docsrva tree (paul:1.3554) | paul | 14 Sep |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 0.470 sec. using MySQL 5.1.14-beta-log