| List: | Commits | « Previous MessageNext Message » | |
| From: | jon | Date: | July 29 2008 11:37am |
| Subject: | svn commit - mysqldoc@docsrva: r11409 - trunk/dynamic-docs/changelog | ||
| View as plain text | |||
Author: jstephens Date: 2008-07-29 11:36:59 +0200 (Tue, 29 Jul 2008) New Revision: 11409 Log: Remainder of WL#4169 work (changelog cleanup). Modified: trunk/dynamic-docs/changelog/mysqld.xml Modified: trunk/dynamic-docs/changelog/mysqld.xml =================================================================== --- trunk/dynamic-docs/changelog/mysqld.xml 2008-07-29 09:08:30 UTC (rev 11408) +++ trunk/dynamic-docs/changelog/mysqld.xml 2008-07-29 09:36:59 UTC (rev 11409) Changed blocks: 392, Lines Added: 1311, Lines Deleted: 825; 180378 bytes @@ -604,10 +604,11 @@ <para> The <function role="sql">ExtractValue()</function> and - <function role="sql">UpdateXML()</function> functions performed - extremely slowly for large amounts of XML data (greater than 64 - KB). These functions now execute approximately 2000 times faster - than previously. + <function + role="sql">UpdateXML()</function> functions + performed extremely slowly for large amounts of XML data + (greater than 64 KB). These functions now execute approximately + 2000 times faster than previously. </para> </message> @@ -3797,7 +3798,8 @@ <literal>falcon_record_scavenge_floor</literal> and <literal>falcon_inital_allocation</literal> parameters are now used to control the caching of records in memory within Falcon. - See <xref linkend="se-falcon-configuration"/>. + See <xref + linkend="se-falcon-configuration"/>. </para> </message> @@ -4359,11 +4361,13 @@ <literal>MASTER_HEARTBEAT_PERIOD = <replaceable>interval</replaceable></literal> clause for the <literal>CHANGE MASTER TO</literal> statement (see - <xref linkend="change-master-to"/>); monitoring can be done by - checking the values of the status variables + <xref + linkend="change-master-to"/>); monitoring can be + done by checking the values of the status variables <literal>Slave_heartbeat_period</literal> and <literal>Slave_received_heartbeats</literal> (see - <xref linkend="server-status-variables"/>). + <xref + linkend="server-status-variables"/>). </para> <para> @@ -4533,8 +4537,8 @@ <message> <para> - Fixed a problem where a stored procedure caused a server crash - if the query cache was enabled. + A stored procedure run while the query cache was enabled could + cause the server to crash. </para> </message> @@ -5236,7 +5240,8 @@ written to the binary log, which affects replication and data recovery options. Stored routine-related statements now are logged, subject to the issues and limitations discussed in - <xref linkend="stored-procedure-logging"/>. + <xref + linkend="stored-procedure-logging"/>. </para> </message> @@ -5391,11 +5396,10 @@ <message> <para> - Fixed a bug that caused concurrent inserts to be allowed into - the tables in the <literal>SELECT ... UNION ...</literal> part - of <literal>INSERT ... SELECT ... UNION ...</literal>. This - could result in the incorrect order of queries in the binary - log. + Concurrent inserts were allowed into the tables in the + <literal>SELECT</literal> part of <literal>INSERT ... SELECT ... + UNION ...</literal>. This could result in the incorrect order of + queries in the binary log. </para> </message> @@ -5595,9 +5599,9 @@ <message> <para> - Fixed a rare error condition that caused the slave SQL thread - spuriously to print the message <literal>Binlog has bad magic - number</literal> and stop when it was not necessary to do so. + A rare error condition caused the slave SQL thread spuriously to + print the message <errortext>Binlog has bad magic + number</errortext> and stop when it was not necessary to do so. </para> </message> @@ -5692,8 +5696,9 @@ <para> The performance of boolean full-text searches (using the <quote>+</quote> Operator) has been improved. See - <xref linkend="fulltext-search"/>, for more details about - full-text searching. (Author: Sergey Vojtovich) + <xref + linkend="fulltext-search"/>, for more details + about full-text searching. (Author: Sergey Vojtovich) </para> </message> @@ -6081,8 +6086,8 @@ <message> <para> - Fixed some problems with <command>myisampack</command> on 64-bit - systems that resulted in segmentation violations. + <command>myisampack</command> run on 64-bit systems resulted in + segmentation violations. </para> </message> @@ -6108,10 +6113,10 @@ <message> <para> - Queries with subqueries in <literal>FROM</literal> clause locks - all tables at once for now. This also fixed bugs in - <literal>EXPLAIN</literal> of subqueries in - <literal>FROM</literal> output. + Queries with subqueries in the <literal>FROM</literal> clause + now lock all tables at once. <literal>EXPLAIN</literal> of + subqueries in <literal>FROM</literal> output was also not + handled correctly. </para> </message> @@ -6592,8 +6597,9 @@ <para> <function role="sql">ISNULL(DATE(NULL))</function> and - <function role="sql">ISNULL(CAST(NULL AS DATE))</function> - erroneously returned false. + <function + role="sql">ISNULL(CAST(NULL AS + DATE))</function> erroneously returned false. </para> </message> @@ -6730,7 +6736,8 @@ <message> <para> - Fixed unknown error when negative value bind to unsigned. + Attempting to bind a negative value bind to unsigned caused an + <errortext>Unknown error</errortext>. </para> </message> @@ -6930,7 +6937,8 @@ arguments larger than 256 produce multiple characters. They are no longer interpreted modulo 256 to produce a single character each. These changes may cause some incompatibilities, as noted - in <xref linkend="upgrading-from-4-1"/>. + in <xref + linkend="upgrading-from-4-1"/>. </para> </message> @@ -7493,11 +7501,11 @@ <message> <para> - Fixed bug of re-execution optimized + Re-execution of optimized <function role="sql">COUNT(*)</function>, - <function role="sql">MAX()</function> and - <function role="sql">MIN()</function> functions in prepared - statements. + <function role="sql">MAX()</function>, and + <function role="sql">MIN()</function> functions is now handled + correctly for prepared statements. </para> </message> @@ -7604,7 +7612,8 @@ Replication and <command>mysqlbinlog</command> now have better support for the case that the session character set and collation variables are changed within a given session. See - <xref linkend="replication-features"/>. + <xref + linkend="replication-features"/>. </para> </message> @@ -7742,12 +7751,14 @@ <literal>character_set_connection</literal> and <literal>collation_connection</literal> system variables. For an argument <replaceable>n</replaceable> to - <function role="sql">CHAR()</function>, the result is + <function role="sql" + >CHAR()</function>, the result is <replaceable>n</replaceable> mod 256 for single-byte character sets. For multi-byte character sets, <replaceable>n</replaceable> must be a valid code point in the character set. Also, the result string from - <function role="sql">CHAR()</function> is checked for + <function role="sql" + >CHAR()</function> is checked for well-formedness. For invalid arguments, or a result that is not well-formed, MySQL generates a warning (or, in strict SQL mode, an error). @@ -7791,8 +7802,9 @@ For existing views that were defined using <literal>IS [NOT] {TRUE|FALSE}</literal> constructs, there is a related implication. The definitions of such views were stored using the - <function role="sql">IF()</function> expression, not the - original construct. This is manifest in that <literal>SHOW + <function role="sql" + >IF()</function> expression, not + the original construct. This is manifest in that <literal>SHOW CREATE VIEW</literal> shows the transformed <function role="sql">IF()</function> expression, not the original one. Existing views will evaluate correctly after the @@ -7901,8 +7913,7 @@ <message> <para> - Fix a problem with truncation of <literal>FLOAT</literal> - values. + <literal>FLOAT</literal> values were not truncated correctly. </para> </message> @@ -8070,8 +8081,10 @@ <para> The <function role="sql">SEC_TO_TIME()</function> and - <function role="sql">QUARTER()</function> functions sometimes - did not handle <literal>NULL</literal> values correctly. + <function + role="sql">QUARTER()</function> functions + sometimes did not handle <literal>NULL</literal> values + correctly. </para> </message> @@ -8120,9 +8133,9 @@ <message> <para> - Fixed a bug in authentication code that allowed a malicious user - to crash the server with specially crafted packets (using a - modified client library). + Using a modified client library, a malicious user could take + advantage of an issue in MySQL authentication code to crash the + server with specially crafted packets. </para> </message> @@ -8233,7 +8246,8 @@ <para> The optimizer failed to use equality propagation for - <function role="sqlop">BETWEEN</function> and + <function + role="sqlop">BETWEEN</function> and <literal>IN</literal> predicates with string arguments. </para> @@ -8491,7 +8505,8 @@ The <literal>DECIMAL</literal> and <literal>NUMERIC</literal> data types now are handled with a fixed-point library that allows for precision math handling that results in more accurate - results. See <xref linkend="precision-math"/>. + results. See <xref + linkend="precision-math"/>. </para> <para> @@ -8520,14 +8535,16 @@ with a type of <literal>DECIMAL_RESULT</literal>. If you upgrade to 5.0.3 and find that your UDF now receives string values, use the initialization function to coerce the arguments to numbers - as described in <xref linkend="udf-arguments"/>. + as described in <xref + linkend="udf-arguments"/>. </para> <para> For the <function role="sql">FLOOR()</function> and - <function role="sql">CEILING()</function> functions, the return - type is no longer always <literal>BIGINT</literal>. For - exact-value numeric arguments, the return value has an + <function + role="sql">CEILING()</function> functions, + the return type is no longer always <literal>BIGINT</literal>. + For exact-value numeric arguments, the return value has an exact-value numeric type. For string or floating-point arguments, the return value has a floating-point type. </para> @@ -8704,8 +8721,8 @@ <message> <para> - <literal>InnoDB</literal>: Fix bug in MySQL/InnoDB 5.0.3: SQL - statements were not rolled back on error. + <literal>InnoDB</literal>: SQL statements were not rolled back + on error. </para> </message> @@ -8845,10 +8862,9 @@ <message> <para> - For <literal>InnoDB</literal>, fixed consistent-read behavior of - the first read statement, if the read was served from the query - cache, for the <literal>READ COMMITTED</literal> isolation - level. + <literal>InnoDB</literal>: The first read statement, if served + from the query cache, was not consistent with the <literal>READ + COMMITTED</literal> isolation level. </para> </message> @@ -8958,7 +8974,8 @@ The binary log file and binary log index file now are handled the same way as <literal>MyISAM</literal> tables when there is a <quote>disk full</quote> or <quote>quota exceeded</quote> error. - See <xref linkend="full-disk"/>. + See <xref + linkend="full-disk"/>. </para> </message> @@ -9421,9 +9438,11 @@ <para> The signature of the - <function role="capi">mysql_stmt_prepare()</function> function - was changed to <literal>int mysql_stmt_prepare(MYSQL_STMT *stmt, - const char *query, unsigned long length)</literal>. To create a + <function role="capi" + >mysql_stmt_prepare()</function> + function was changed to <literal>int + mysql_stmt_prepare(MYSQL_STMT *stmt, const char *query, unsigned + long length)</literal>. To create a <literal>MYSQL_STMT</literal> handle, you should use the <function role="capi">mysql_stmt_init()</function> function, not <function role="capi">mysql_stmt_prepare()</function>. @@ -9617,8 +9636,10 @@ <message> <para> - Fixed a lot of bugs in - <function role="sql">GROUP_CONCAT()</function>. + The <function role="sql">GROUP_CONCAT()</function> had a number + of issues with <literal>ORDER BY</literal> and + <literal>DISTINCT</literal>, and with <literal>GROUP + BY</literal> in subqueries. </para> </message> @@ -9705,8 +9726,9 @@ <para> Incorrect results when searching using - <function role="sql">IN()</function> where search items included - <literal>NULL</literal> and <literal>0</literal>. + <function role="sql" + >IN()</function> where search items + included <literal>NULL</literal> and <literal>0</literal>. </para> </message> @@ -9763,7 +9785,8 @@ <literal>MINUTE_MICROSECOND</literal>, <literal>SECOND_MICROSECOND</literal>, and <literal>MICROSECOND</literal> for - <function role="sql">DATE_ADD()</function>, + <function role="sql" + >DATE_ADD()</function>, <function role="sql">DATE_SUB()</function>, and <function role="sql">EXTRACT()</function>. </para> @@ -10019,7 +10042,8 @@ <para> The behavior of <literal>LOAD DATA INFILE</literal> in this regard was changed again in MySQL 5.0.26. See - <xref linkend="news-5-0-26"/>. + <xref + linkend="news-5-0-26"/>. </para> </important> @@ -10044,8 +10068,8 @@ <message> <para> - Fixed a hang in full-text indexing of strings in multi-byte (all - besides <literal>utf8</literal>) charsets. + Full-text indexing of strings in multi-byte (all besides + <literal>utf8</literal>) charsets could sometimes hang. </para> </message> @@ -10063,17 +10087,20 @@ </bugs> <versions> + <version ver="4.0.26"/> <version ver="4.1.12"/> + <version ver="5.0.5"/> </versions> <message> <para> - <literal>InnoDB</literal>: Fix assertion failures of type + <literal>InnoDB</literal>: Assertion failures of types <literal>ut_a(cursor->old_stored == BTR_PCUR_OLD_STORED)</literal> and - <literal>prebuilt->template_type == 0</literal>. This bug was - introduced in 4.1.10 and 4.0.24. + <literal>prebuilt->template_type == 0</literal> could occur + when performing multi-table updates. This bug was introduced in + 4.1.10 and 4.0.24. </para> </message> @@ -10329,8 +10356,9 @@ <message> <para> - Fixed a bug in <literal>SHOW GRANTS</literal> and - <literal>EXPLAIN SELECT</literal> character set conversion. + <literal>SHOW GRANTS</literal> and <literal>EXPLAIN + SELECT</literal> did not always perform character set conversion + correctly. </para> </message> @@ -10403,9 +10431,10 @@ <para> When <function role="sql">NOW()</function> was used in a - <function role="sqlop">BETWEEN</function> clause of the - definition for a view, it was replaced with a constant in the - view. + <function + role="sqlop">BETWEEN</function> clause of + the definition for a view, it was replaced with a constant in + the view. </para> </message> @@ -10681,7 +10710,8 @@ <para> See - <xref linkend="mysql-cluster-replication-conflict-resolution"/>, + <xref linkend="mysql-cluster-replication-conflict-resolution" + />, for more information. </para> @@ -10791,8 +10821,10 @@ <para> The <function role="sql">ENCRYPT()</function> and - <function role="sql">SUBSTRING_INDEX()</function> functions - would cause errors when used with a <literal>VIEW</literal>. + <function + role="sql">SUBSTRING_INDEX()</function> + functions would cause errors when used with a + <literal>VIEW</literal>. </para> </message> @@ -10889,9 +10921,10 @@ <message> <para> - Fixed a crash in <function role="sql">CONVERT_TZ()</function> - function when its second or third argument was from a - <literal>const</literal> table (see <xref linkend="explain"/>). + The <function role="sql">CONVERT_TZ()</function> function, when + its second or third argument was from a <literal>const</literal> + table, caused the server to crash. (See + <xref linkend="explain"/>.) </para> </message> @@ -10985,8 +11018,7 @@ <message> <para> - Fixed a bug in <literal>REPAIR TABLE</literal> that resulted - sometimes in a corrupted table, if the table contained + <literal>REPAIR TABLE</literal> could corrupt a table containing <literal>FULLTEXT</literal> indexes and many words of different lengths that are considered equal (which is possible in certain collations, such as <literal>latin1_german2_ci</literal> or @@ -11000,6 +11032,7 @@ <logentry entrytype="feature"> <tags> + <highlight type="securityfix"/> <manual type="defaults-file"/> </tags> @@ -11015,8 +11048,7 @@ <para> The <option>--defaults-file=<replaceable>file_name</replaceable> - </option> option now requires that the filename must exist - (safety fix). + </option> option now requires that the filename must exist. </para> </message> @@ -11069,9 +11101,9 @@ <message> <para> - Fixed bug which caused different number of warnings to be - generated when bad datetime as string or as number was inserted - into <literal>DATETIME</literal> or <literal>TIMESTAMP</literal> + Different numbers of warnings were generated when an invalid + datetime (as a string or as a number) was inserted into a + <literal>DATETIME</literal> or <literal>TIMESTAMP</literal> column. </para> @@ -11216,8 +11248,10 @@ <message> <para> - Fixed some <command>awk</command> script portability problems in - <command>cmd-line-utils/libedit/makelist.sh</command>. + <command>awk</command> script portability problems were found in + <command> + <filename>cmd-line-utils/libedit/makelist.sh</filename> + </command>. </para> </message> @@ -11246,9 +11280,10 @@ <para> Use of <function role="sql">MIN()</function> or - <function role="sql">MAX()</function> with <literal>GROUP - BY</literal> on a <literal>ucs2</literal> column could cause a - server crash. + <function + role="sql">MAX()</function> with + <literal>GROUP BY</literal> on a <literal>ucs2</literal> column + could cause a server crash. </para> </message> @@ -11447,8 +11482,8 @@ <message> <para> - Fixed a bug that caused libmysql to crash when attempting to - fetch a value of <literal>MEDIUMINT</literal> column. + <literal>libmysql</literal> crashed when attempting to fetch the + value of a <literal>MEDIUMINT</literal> column. </para> </message> @@ -11588,8 +11623,8 @@ <message> <para> - Fixed a crash caused by - <function role="sql">UNHEX(NULL)</function>. + Executing <function role="sql">UNHEX(NULL)</function> caused the + server to crash. </para> </message> @@ -11643,8 +11678,8 @@ <message> <para> - Fixed processing of <function role="sql">RAND()</function> in - subqueries with static tables. + Processing of <function role="sql">RAND()</function> in + subqueries with static tables was not always handled correctly. </para> </message> @@ -11953,8 +11988,9 @@ <para> The <literal>LOAD DATA FROM MASTER</literal> and <literal>LOAD TABLE FROM MASTER</literal> statements are deprecated. See - <xref linkend="load-data-from-master"/>, for recommended - alternatives. + <xref + linkend="load-data-from-master"/>, for + recommended alternatives. </para> </message> @@ -12059,7 +12095,9 @@ With mixed-format binary logging, <literal>INSERT DELAYED</literal> statements were logged using statement-based logging, and they did not replicate properly for statements that - used values such as <function role="sql">UUID()</function>, + used values such as + <function + role="sql">UUID()</function>, <function role="sql">RAND()</function>, or user-defined variables that require row-based logging. To correct this, the <literal>DELAYED</literal> handler thread how switches to @@ -12403,10 +12441,10 @@ <message> <para> - Fixed that, when encountering a <quote>disk full</quote> or - <quote>quota exceeded</quote> write error, - <literal>MyISAM</literal> sometimes didn't sleep and retry the - write, thus resulting in a corrupted table. + When encountering a <errortext>disk full</errortext> or + <errortext>quota exceeded</errortext> write error, + <literal>MyISAM</literal> sometimes failed to sleep and retry + the write, resulting in a corrupted table. </para> </message> @@ -12492,10 +12530,10 @@ <message> <para> - Fixed that when a <literal>Rotate</literal> event is found by - the slave SQL thread in the middle of a transaction, the value - of <literal>Relay_Log_Pos</literal> in <literal>SHOW SLAVE - STATUS</literal> remains correct. + When a <literal>Rotate</literal> event was found by the slave + SQL thread in the middle of a transaction, the value of + <literal>Relay_Log_Pos</literal> in <literal>SHOW SLAVE + STATUS</literal> was incorrectly altered. </para> </message> @@ -12583,9 +12621,8 @@ <message> <para> - Fixed a problem with the <literal>tee</literal> command in - <command>mysql</command> that resulted in - <command>mysql</command> crashing. + The <literal>tee</literal> command could sometimes cause the + <command>mysql</command> client to crash. </para> </message> @@ -12613,10 +12650,11 @@ <para> When using the result of - <function role="sql">SEC_TO_TIME()</function> for time value - greater than 24 hours in an <literal>ORDER BY</literal> clause, - either directly or through a column alias, the rows were sorted - incorrectly as strings. + <function role="sql" + >SEC_TO_TIME()</function> for time + value greater than 24 hours in an <literal>ORDER BY</literal> + clause, either directly or through a column alias, the rows were + sorted incorrectly as strings. </para> </message> @@ -12728,9 +12766,9 @@ <message> <para> - Fixed a bug in <function role="sql">CONV()</function> function - returning unsigned <literal>BIGINT</literal> number (third - argument is positive, and return value does not fit in 32 bits). + The <function role="sql">CONV()</function> function returned an + unsigned <literal>BIGINT</literal> number, which does not fit in + 32 bits. </para> </message> @@ -12757,12 +12795,12 @@ <message> <para> - Fixed a bug in <literal>MATCH ... AGAINST</literal> in natural - language mode that could cause a server crash if the - <literal>FULLTEXT</literal> index was not used in a join - (<literal>EXPLAIN</literal> did not show + <literal>MATCH ... AGAINST</literal> in natural language mode + could cause a server crash if the <literal>FULLTEXT</literal> + index was not used in a join (that is, + <literal>EXPLAIN</literal> did not show <literal>fulltext</literal> join mode) and the search query - matched no rows in the table . + matched no rows in the table. </para> </message> @@ -13202,7 +13240,8 @@ <para> For more information regarding these changes, see - <xref linkend="events-overview"/>. + <xref + linkend="events-overview"/>. </para> </message> @@ -13251,7 +13290,8 @@ <para> The <literal>ft_boolean_syntax</literal> variable now can be changed while the server is running. See - <xref linkend="server-system-variables"/>. + <xref + linkend="server-system-variables"/>. </para> </message> @@ -13405,8 +13445,8 @@ <message> <para> - Fixed a crash of the MySQL slave server when it was built with - <option>--with-debug</option> and replicating itself. + A MySQL slave server built using <option>--with-debug</option>, + and replicating itself, crashed. </para> </message> @@ -13460,8 +13500,8 @@ <message> <para> - Fixed a collation coercibility problem that caused a union - between binary and non-binary columns to fail. + Unions between binary and non-binary columns failed due to a a + collation coercibility problem. </para> </message> @@ -13598,10 +13638,10 @@ <message> <para> - Fixed a bug that omitted the <filename>.err</filename> extension - of the error log file (<option>--log-error</option>) when the - hostname contained a domain name. The domain name is now - replaced by the extension. + The <filename>.err</filename> extension was omitted from the + error log file (<option>--log-error</option>) when the hostname + contained a domain name. The domain name is now replaced by the + extension. </para> </message> @@ -13697,7 +13737,9 @@ <para> Triggers can now reference tables by name. See - <xref linkend="create-trigger"/>, for more information. + <xref + linkend="create-trigger"/>, for more + information. </para> </message> @@ -13809,9 +13851,9 @@ <message> <para> - Fixed calculation of <literal>Index_length</literal> in - <literal>HEAP</literal> table status for - <literal>BTREE</literal> indexes. + <literal>Index_length</literal> in <literal>HEAP</literal> table + status for <literal>BTREE</literal> indexes was not calculated + correctly. </para> </message> @@ -13862,11 +13904,11 @@ <message> <para> - Fix the way that Instance Manager finds the version number of - instances, so that it works properly when the executable name - isn't the same as what the Instance Manager launched (such as - when wrapping a <command>libtool</command>-wrapped executable - from the source tree). + Instance Manager now finds the version numbers, so that it works + properly when the executable name isn't the same as what the + Instance Manager launched (such as when wrapping a + <command>libtool</command>-wrapped executable from the source + tree). </para> </message> @@ -13921,7 +13963,8 @@ <para> For more information, see - <xref linkend="ndb-mgm-get-clusterlog-loglevel"/>. + <xref + linkend="ndb-mgm-get-clusterlog-loglevel"/>. </para> </message> @@ -14085,10 +14128,11 @@ <literal>IGNORE_SPACE</literal> was reduced significantly in MySQL 5.1.13, from about 200 to about 30. (For details about <literal>IGNORE_SPACE</literal>, see - <xref linkend="function-resolution"/>.) This change improves the - consistency of parser operation. However, it also introduces the - possibility of incompatibility for old SQL code that relies on - the following conditions: + <xref + linkend="function-resolution"/>.) This change + improves the consistency of parser operation. However, it also + introduces the possibility of incompatibility for old SQL code + that relies on the following conditions: </para> <itemizedlist> @@ -14104,8 +14148,9 @@ The presence or absence of whitespace following a function name is used to distinguish between a built-in function and stored function that have the same name (for example, - <function role="sql">PI()</function> versus <literal>PI - ()</literal>). + <function role="sql" + >PI()</function> versus + <literal>PI ()</literal>). </para> </listitem> @@ -14160,9 +14205,9 @@ <message> <para> - Fix conversion of strings -> double to get higher accuracy - for floating point values that are integers, like: - <literal>123.45E+02</literal> . + Conversion of strings to doubles is now more accurate for + floating point values that can be represented by integers, such + as <literal>123.45E+02</literal>. </para> </message> @@ -14484,11 +14529,12 @@ <message> <para> - Fixed <literal>SHOW TABLES</literal> output field name and - values according to standard. Field name changed from - <literal>Type</literal> to <literal>table_type</literal>, values - are <literal>BASE TABLE</literal>, <literal>VIEW</literal> and - <literal>ERROR</literal>. + The <literal>Type</literal> column name and values in the output + from <literal>SHOW TABLES</literal> are now shown according to + standard. The column name has changed from + <literal>Type</literal> to <literal>table_type</literal>; + permitted values are <literal>BASE TABLE</literal>, + <literal>VIEW</literal>, and <literal>ERROR</literal>. </para> </message> @@ -14535,7 +14581,8 @@ Added <literal>SELECT INTO <replaceable>list_of_vars</replaceable></literal>, which can be of mixed (that is, global and local) types. See - <xref linkend="select-into-statement"/>. + <xref + linkend="select-into-statement"/>. </para> </message> @@ -14592,7 +14639,8 @@ With <literal>ONLY_FULL_GROUP_BY</literal> enables, the server was too strict: Some expressions involving only aggregate values were rejected as non-aggregate (for example, - <function role="sql">MAX(a)</function> − + <function role="sql" + >MAX(a)</function> − <function role="sql">MIN(a)</function>). </para> @@ -14766,7 +14814,8 @@ <para> For additional information, see - <xref linkend="events-privileges"/>. + <xref linkend="events-privileges" + />. </para> </message> @@ -14831,10 +14880,11 @@ <para> (You must use <literal>/</literal> characters when specifying paths for these options, regardless of platform. See - <xref linkend="partitioning-overview"/>, for an example using - absolute paths for <literal>DATA DIRECTORY</literal> and - <literal>INDEX DIRECTORY</literal> when creating a partitioned - table on Windows.) + <xref + linkend="partitioning-overview"/>, for an + example using absolute paths for <literal>DATA + DIRECTORY</literal> and <literal>INDEX DIRECTORY</literal> when + creating a partitioned table on Windows.) </para> </message> @@ -15033,8 +15083,7 @@ <message> <para> - A memory leak in the event scheduler that was uncovered by - Valgrind was fixed. + A memory leak in the event scheduler was uncovered by Valgrind. </para> </message> @@ -15140,8 +15189,8 @@ <message> <para> - Fixed a server crash caused by use of - <function role="sql">NOW()</function> is a subquery. + Using <function role="sql">NOW()</function> in a subquery caused + the server to crash. </para> </message> @@ -15167,8 +15216,8 @@ <message> <para> - Fixed a problem resolving table names with - <literal>lower_case_table_names=2</literal> when the table name + Table names were not handled correctly when + <literal>lower_case_table_names=2</literal> if the table name lettercase differed in the <literal>FROM</literal> and <literal>WHERE</literal> clauses. </para> @@ -15253,10 +15302,10 @@ <message> <para> - Fixed a bug which caused <literal>TIMESTAMP</literal> columns - with display width specified to be not identical to - <literal>DATETIME</literal> columns when server was run in - <literal>MAXDB</literal> mode . + <literal>TIMESTAMP</literal> columns with their display width so + specified were not treated as identical to + <literal>DATETIME</literal> columns when the server was run in + <literal>MAXDB</literal> mode. </para> </message> @@ -15303,9 +15352,8 @@ <message> <para> - Fixed a bug that caused the server to sometimes choose - non-optimal execution plan for a prepared statement executed - with changed placeholder values. + The server sometimes chose a non-optimal execution plan for a + prepared statement executed with changed placeholder values. </para> </message> @@ -15550,13 +15598,19 @@ <para> The patch for Bug #8303 broke the fix for Bug #8378 and was - undone. (In string literals with an escape character + reverted. + </para> + + <para> + In string literals with an escape character (<literal>\</literal>) followed by a multi-byte character that - has a second byte of (<literal>\</literal>), the literal was not - interpreted correctly. The next byte now is escaped, not the - entire multi-byte character. This means it a strict reverse of - the <function role="capi">mysql_real_escape_string()</function> - function.) + had (<literal>\</literal>) as its second byte, the literal was + not interpreted correctly. Now only next byte now is escaped, + and not the entire multi-byte character. This means it a strict + reverse of the + <function role="capi" + >mysql_real_escape_string()</function> + function. </para> </message> @@ -15610,9 +15664,11 @@ <para> The functions <function role="sql">COALESCE()</function>, - <function role="sql">IF()</function>, and - <function role="sql">IFNULL()</function> performed incorrect - conversions of their arguments. + <function + role="sql">IF()</function>, and + <function role="sql" + >IFNULL()</function> performed + incorrect conversions of their arguments. </para> </message> @@ -15661,7 +15717,8 @@ creation time of <literal>InnoDB</literal> tables. That this timestamp might not always be correct because (for example) it was changed by <literal>ALTER TABLE</literal>. See - <xref linkend="innodb-restrictions"/>. + <xref + linkend="innodb-restrictions"/>. </para> </message> @@ -15769,10 +15826,10 @@ <message> <para> - Fixed the <literal>Exec_master_log_pos</literal> column and its - disk image in the <filename>relay-log.info</filename> file to be - correct if the master had version 3.23. (The value was too big - by six bytes.) This bug does not exist in MySQL 5.0. + The <literal>Exec_master_log_pos</literal> column and its disk + image in the <filename>relay-log.info</filename> were not + handled correctly if the master had version 3.23. (The value was + too big by six bytes.) This bug does not exist in MySQL 5.0. </para> </message> @@ -15799,7 +15856,7 @@ <message> <para> - <command>mysql_fix_privilege_tables</command> did not handle a + <command>mysql_fix_privilege_tables</command> did not accept a password containing embedded space or apostrophe characters. </para> @@ -15807,8 +15864,6 @@ </logentry> -<!-- WL#4169 EDITS THROUGH HERE --> - <logentry entrytype="bug"> <tags> @@ -16296,8 +16351,9 @@ <para> A potential memory overrun could occur in - <function role="capi">mysql_real_connect()</function> (which - required a compromised DNS server and certain operating + <function role="capi" + >mysql_real_connect()</function> + (which required a compromised DNS server and certain operating systems). </para> @@ -16512,9 +16568,12 @@ <para> When used in defining a view, the - <function role="sql">TIME_FORMAT()</function> function failed - with calculated values, for example, when passed the value - returned by <function role="sql">SEC_TO_TIME()</function>. + <function role="sql" + >TIME_FORMAT()</function> + function failed with calculated values, for example, when passed + the value returned by + <function role="sql" + >SEC_TO_TIME()</function>. </para> </message> @@ -16623,7 +16682,9 @@ </listitem> </itemizedlist> - For more information, see <xref linkend="status-table"/>, + For more information, see + <xref linkend="status-table" + />, <xref linkend="variables-table"/>. </para> @@ -16757,10 +16818,12 @@ <para> <function role="capi">mysql_stmt_fetch()</function> and - <function role="capi">mysql_stmt_store_result()</function> could - hang if they were called without a prior call to - <function role="capi">mysql_stmt_execute()</function>. Now they - give an error instead. + <function + role="capi">mysql_stmt_store_result()</function> + could hang if they were called without a prior call to + <function role="capi" + >mysql_stmt_execute()</function>. + Now they give an error instead. </para> </message> @@ -16812,8 +16875,9 @@ <para> A new <literal>listEvents()</literal> method has been added to the <literal>Dictionary</literal> class. See - <xref linkend="class-dictionary-listevents"/>, for more - information. + <xref + linkend="class-dictionary-listevents"/>, for + more information. </para> </message> @@ -16841,10 +16905,11 @@ A number of performance issues were resolved that had previously been encountered when using statements that repeatedly invoked stored functions. For example, calling - <function role="sql">BENCHMARK()</function> using a stored - function executed much more slowly than when invoking it with - inline code that accomplished the same task. In most cases the - two should now execute with approximately the same speed. + <function role="sql" + >BENCHMARK()</function> using a + stored function executed much more slowly than when invoking it + with inline code that accomplished the same task. In most cases + the two should now execute with approximately the same speed. </para> </message> @@ -17415,9 +17480,10 @@ <para> Resolution of the argument to the - <function role="sql">VALUES()</function> function to a variable - inside a stored routine caused a server crash. The argument must - be a table column. + <function role="sql" + >VALUES()</function> function to a + variable inside a stored routine caused a server crash. The + argument must be a table column. </para> </message> @@ -18062,7 +18128,8 @@ <para> Added SQL syntax for prepared statements. See - <xref linkend="sql-syntax-prepared-statements"/>. + <xref + linkend="sql-syntax-prepared-statements"/>. </para> </message> @@ -18332,7 +18399,8 @@ <option>--bind-address</option> makes it possible to restrict management client connections to <command>ndb_mgmd</command> to a single host and port. For more information, see - <xref linkend="mysql-cluster-ndb-mgmd-command-options"/>. + <xref + linkend="mysql-cluster-ndb-mgmd-command-options"/>. </para> </message> @@ -18822,7 +18890,8 @@ </itemizedlist> For details of these changes, see - <xref linkend="mysql-cluster-restore"/>. + <xref + linkend="mysql-cluster-restore"/>. </para> </message> @@ -19326,8 +19395,11 @@ Various types of preprocessing using SQL functions are now possible when loading XML. For example, you can concatenate two XML tag or attribute values into a single column value using - <function role="sql">CONCAT()</function>, or remove some parts - of the data using <function role="sql">REPLACE()</function>. + <function role="sql" + >CONCAT()</function>, or remove + some parts of the data using + <function + role="sql">REPLACE()</function>. </para> </message> @@ -19826,7 +19898,8 @@ <para> Use of - <function role="sql">GROUP_CONCAT(<replaceable>x</replaceable>)</function> + <function role="sql" + >GROUP_CONCAT(<replaceable>x</replaceable>)</function> in a subquery, where <replaceable>x</replaceable> was an alias to a column in the outer query, resulted in a server crash. </para> @@ -19866,7 +19939,8 @@ <para> See - <xref linkend="mysql-cluster-upgrade-downgrade-compatibility"/>, + <xref linkend="mysql-cluster-upgrade-downgrade-compatibility" + />, and related sections of the Manual before upgrading a MySQL Cluster to version 5.1.12 or later. </para> @@ -20010,8 +20084,11 @@ <para> Added new <function role="sql">COMPRESS()</function>, - <function role="sql">UNCOMPRESS()</function>, and - <function role="sql">UNCOMPRESSED_LENGTH()</function> functions. + <function + role="sql">UNCOMPRESS()</function>, and + <function role="sql" + >UNCOMPRESSED_LENGTH()</function> + functions. </para> </message> @@ -20322,9 +20399,9 @@ <para> When used within a subquery, - <function -role="sql">SUBSTRING()</function> returned an empty - string. + <function role="sql" + >SUBSTRING()</function> returned an + empty string. </para> </message> @@ -20406,15 +20483,18 @@ <para> The XPath operators <literal><</literal> and <literal>></literal>, as implemented in the - <function role="sql">ExtractValue()</function> function, - operated in reverse. + <function + role="sql">ExtractValue()</function> + function, operated in reverse. </para> <para> With this fix, all standard XPath comparison operators should now be supported correctly for use with the - <function role="sql">ExtractValue()</function> and - <function role="sql">UpdateXML()</function> functions. + <function role="sql" + >ExtractValue()</function> and + <function role="sql" + >UpdateXML()</function> functions. </para> </message> @@ -20441,7 +20521,9 @@ Updates were being written to the binary log when there were <literal>binlog-do-db</literal> or <literal>binlog-ignore-db</literal> options even when there was - no current database, contrary to <xref linkend="binary-log"/>. + no current database, contrary to + <xref + linkend="binary-log"/>. </para> </message> @@ -21495,8 +21577,9 @@ <para> For a query with both <literal>GROUP BY</literal> and - <function role="sql">COUNT(DISTINCT)</function> clauses and a - <literal>FROM</literal> clause with a subquery, + <function + role="sql">COUNT(DISTINCT)</function> + clauses and a <literal>FROM</literal> clause with a subquery, <literal>NULL</literal> was returned for any <literal>VARCHAR</literal> column selected by the subquery. </para> @@ -21524,8 +21607,9 @@ <para> The warning message from - <function role="sql">GROUP_CONCAT()</function> did not always - indicate the correct number of lines. + <function role="sql" + >GROUP_CONCAT()</function> did not + always indicate the correct number of lines. </para> </message> @@ -21825,10 +21909,12 @@ <para> <function role="sql">TIMEDIFF()</function>, - <function role="sql">ADDTIME()</function>, and - <function role="sql">STR_TO_DATE()</function> were not reporting - that they could return <literal>NULL</literal>, so functions - that invoked them might misinterpret their results. + <function role="sql" + >ADDTIME()</function>, and + <function role="sql" + >STR_TO_DATE()</function> were not + reporting that they could return <literal>NULL</literal>, so + functions that invoked them might misinterpret their results. </para> </message> @@ -22279,10 +22365,12 @@ <para> Redundant binary log <literal>LAST_INSERT_ID</literal> events could be generated; - <function role="sql">LAST_INSERT_ID(<replaceable>expr</replaceable>)</function> + <function role="sql" + >LAST_INSERT_ID(<replaceable>expr</replaceable>)</function> did not return the value of <replaceable>expr</replaceable>; - <function role="sql">LAST_INSERT_ID()</function> could return - the value generated by the current statement if the call + <function + role="sql">LAST_INSERT_ID()</function> could + return the value generated by the current statement if the call occurred after value generation, as in: </para> @@ -22407,8 +22495,9 @@ <para> The thread ID was not reset properly after execution of - <function role="capi">mysql_change_user()</function>, which - could cause replication failure when replicating temporary + <function + role="capi">mysql_change_user()</function>, + which could cause replication failure when replicating temporary tables. </para> @@ -22524,8 +22613,9 @@ <para> Using <literal>ORDER BY</literal> to sort the results of an <function role="sql">IF()</function> that contained a - <function role="sql">FROM_UNIXTIME()</function> expression - returned incorrect results due to integer overflow. + <function + role="sql">FROM_UNIXTIME()</function> + expression returned incorrect results due to integer overflow. </para> </message> @@ -22631,7 +22721,8 @@ <para> Functions that evaluate to constants (such as - <function role="sql">NOW()</function> and + <function role="sql" + >NOW()</function> and <function role="sql">CURRENT_USER()</function> were being evaluated in the definition of a <literal>VIEW</literal> rather than included verbatim. @@ -22726,10 +22817,13 @@ <para> Additional fix for - <function role="capi">mysql_server_init()</function> and - <function role="capi">mysql_server_end()</function> C API - functions so that stopping and restarting the embedded server - would not cause a crash. + <function role="capi" + >mysql_server_init()</function> + and + <function role="capi" + >mysql_server_end()</function> C + API functions so that stopping and restarting the embedded + server would not cause a crash. </para> </message> @@ -23560,8 +23654,11 @@ <para> The <literal>LockPagesInMainMemory</literal> configuration parameter has changed its type and possible values. For more - information, see - <literal><link linkend="mysql-cluster-param-ndbd-definition-lockpagesinmainmemory">LockPagesInMainMemory</link></literal>. + information, see <literal> + <link + linkend="mysql-cluster-param-ndbd-definition-lockpagesinmainmemory" + >LockPagesInMainMemory</link> + </literal>. </para> <important> @@ -23634,9 +23731,10 @@ <para> Using <literal>RANGE</literal> partitioning with a - <function role="sqlop">CASE</function> expression as the - partitioning function would cause records to be placed in the - wrong partition. + <function + role="sqlop">CASE</function> expression as + the partitioning function would cause records to be placed in + the wrong partition. </para> </message> @@ -23870,7 +23968,8 @@ <para> Performing - <function role="sql">DATE(LEFT(<replaceable>column</replaceable>,8))</function> + <function role="sql" + >DATE(LEFT(<replaceable>column</replaceable>,8))</function> on a <literal>DATE</literal> column produces incorrect results. </para> @@ -23925,8 +24024,9 @@ <para> <function role="sql">DATE_ADD()</function> and - <function role="sql">DATE_SUB()</function> were converting - invalid dates to <literal>NULL</literal> in + <function role="sql" + >DATE_SUB()</function> were + converting invalid dates to <literal>NULL</literal> in <literal>TRADITIONAL</literal> SQL mode rather than rejecting them with an error. </para> @@ -24273,7 +24373,8 @@ <para> <literal>disable-local-infile</literal> option had no effect if the client read it from a configuration file using - <function role="capi">mysql_options(...,MYSQL_READ_DEFAULT,...)</function>. + <function role="capi" + >mysql_options(...,MYSQL_READ_DEFAULT,...)</function>. </para> </message> @@ -24363,7 +24464,8 @@ of the log files can be changed by setting the <literal>general_log_file</literal> and <literal>slow_query_log_file</literal> system variables. See - <xref linkend="query-log"/>, and + <xref + linkend="query-log"/>, and <xref linkend="slow-query-log"/>. </para> @@ -25231,7 +25333,9 @@ <para> See <xref linkend="create-event"/>, and - <xref linkend="alter-event"/>, for more specific information. + <xref linkend="alter-event" + />, for more specific + information. </para> </message> @@ -25658,8 +25762,9 @@ <para> Added new - <function role="capi">mysql_get_server_version()</function> C - API client function. + <function role="capi" + >mysql_get_server_version()</function> + C API client function. </para> </message> @@ -26196,9 +26301,10 @@ <literal>SUPER</literal> privilege has changed to a requirement for the <literal>TRIGGER</literal> privilege. After upgrading, be sure to update your grant tables as described in - <xref linkend="mysql-fix-privilege-tables"/>. This process - assigns the <literal>TRIGGER</literal> privilege to all accounts - that had the <literal>SUPER</literal> privilege. (After + <xref + linkend="mysql-fix-privilege-tables"/>. This + process assigns the <literal>TRIGGER</literal> privilege to all + accounts that had the <literal>SUPER</literal> privilege. (After updating, you might also consider whether any of those accounts no longer need <literal>SUPER</literal>.) If you fail to update the grant tables, triggers may fail when activated. @@ -26589,10 +26695,11 @@ <para> When running a query that contained a - <function role="sql">GROUP_CONCAT(SELECT GROUP_CONCAT(...) - )</function>, the result was <literal>NULL</literal> except in - the <literal>ROLLUP</literal> part of the result, if there was - one. + <function role="sql" + >GROUP_CONCAT(SELECT + GROUP_CONCAT(...) )</function>, the result was + <literal>NULL</literal> except in the <literal>ROLLUP</literal> + part of the result, if there was one. </para> </message> @@ -27087,7 +27194,8 @@ Added the <literal>SHOW FUNCTION CODE</literal> and <literal>SHOW PROCEDURE CODE</literal> statements (available only for servers that have been built with debugging support). - See <xref linkend="show-procedure-code"/>. + See <xref + linkend="show-procedure-code"/>. </para> </message> @@ -27151,7 +27259,8 @@ version of MySQL Server and repairs them if necessary. This program should be run for each MySQL upgrade (rather than <command>mysql_fix_privilege_tables</command>). See - <xref linkend="mysql-upgrade"/>. + <xref + linkend="mysql-upgrade"/>. </para> </listitem> @@ -27267,7 +27376,8 @@ <para> The syntax for index hints has been extended to enable explicit specification that the hint applies only to join processing. See - <xref linkend="index-hints"/>. + <xref + linkend="index-hints"/>. </para> <para> @@ -27295,7 +27405,8 @@ The syntax for index hints has been extended to enable more fine-grained control over the optimizer's selection of an execution plan for various phases of query processing. See - <xref linkend="index-hints"/>. + <xref linkend="index-hints" + />. </para> </message> @@ -27878,8 +27989,12 @@ renamed to <literal>cluster</literal>. This will effect replication between MySQL Clusters where one cluster is running MySQL 5.1.8 or later, and the other is running MySQL 5.1.7 or - earlier. See <xref linkend="mysql-cluster-replication"/>, and - especially <xref linkend="mysql-cluster-replication-schema"/>. + earlier. See + <xref + linkend="mysql-cluster-replication"/>, and + especially + <xref + linkend="mysql-cluster-replication-schema"/>. </para> </message> @@ -28021,7 +28136,8 @@ <para> <function role="sql">DATE_ADD()</function> and - <function role="sql">DATE_SUB()</function> returned + <function role="sql" + >DATE_SUB()</function> returned <literal>NULL</literal> when the result date was on the day <literal>'9999-12-31'</literal>. </para> @@ -28329,8 +28445,10 @@ <para> Added the XML functions - <function role="sql">ExtractValue()</function> and - <function role="sql">UpdateXML()</function>. + <function role="sql" + >ExtractValue()</function> and + <function role="sql" + >UpdateXML()</function>. <function role="sql">ExtractValue()</function> returns the content of a fragment of XML matching a given XPath expression. <function role="sql">UpdateXML()</function> replaces the element @@ -28392,7 +28510,8 @@ <para> For <literal>INSERT ... ON DUPLICATE KEY UPDATE</literal>, use of - <function role="sql">VALUES(<replaceable>col_name</replaceable>)</function> + <function role="sql" + >VALUES(<replaceable>col_name</replaceable>)</function> within the <literal>UPDATE</literal> clause sometimes was handled incorrectly. </para> @@ -28451,8 +28570,10 @@ <para> If <function role="sql">COMPRESS()</function> returned <literal>NULL</literal>, subsequent invocations of - <function role="sql">COMPRESS()</function> within a result set - or within a trigger also returned <literal>NULL</literal>. + <function + role="sql">COMPRESS()</function> within a + result set or within a trigger also returned + <literal>NULL</literal>. </para> </message> @@ -28748,7 +28869,9 @@ A new <literal>NdbRecord</literal> object has been added to the <literal>NDB</literal> API. This object provides mapping to a record stored in <literal>NDB</literal>. See - <xref linkend="interface-ndbrecord"/>, for more information. + <xref + linkend="interface-ndbrecord"/>, for more + information. </para> </message> @@ -29428,7 +29551,8 @@ <para> It is now possible to specify the transaction coordinator when starting a transaction. See - <xref linkend="class-ndb-starttransaction"/>, for more + <xref linkend="class-ndb-starttransaction" + />, for more information. </para> @@ -29605,7 +29729,9 @@ The behavior 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 + global). See + <xref + linkend="server-status-variables"/>, for additional information. </para> @@ -29944,7 +30070,8 @@ Methods were added to the <literal>Ndb_cluster_connection</literal> class to faciliate iterating over existing <literal>Ndb</literal> objects. See - <xref linkend="class-ndb-cluster-connection-get-next-ndb-object"/>, + <xref + linkend="class-ndb-cluster-connection-get-next-ndb-object"/>, for more information. </para> @@ -30049,20 +30176,27 @@ <para> Added new <function role="sql">ADDTIME()</function>, - <function role="sql">DATE()</function>, - <function role="sql">DATEDIFF()</function>, + <function + role="sql">DATE()</function>, + <function role="sql" + >DATEDIFF()</function>, <function role="sql">LAST_DAY()</function>, <function role="sql">MAKEDATE()</function>, - <function role="sql">MAKETIME()</function>, + <function role="sql" + >MAKETIME()</function>, <function role="sql">MICROSECOND()</function>, <function role="sql">SUBTIME()</function>, - <function role="sql">TIME()</function>, + <function role="sql" + >TIME()</function>, <function role="sql">TIMEDIFF()</function>, <function role="sql">TIMESTAMP()</function>, - <function role="sql">UTC_DATE()</function>, + <function role="sql" + >UTC_DATE()</function>, <function role="sql">UTC_TIME()</function>, <function role="sql">UTC_TIMESTAMP()</function>, and - <function role="sql">WEEKOFYEAR()</function> functions. + <function + role="sql">WEEKOFYEAR()</function> + functions. </para> </message> @@ -30288,7 +30422,8 @@ The server would allow foreign keys to be declared in the definition of a partitioned table despite the fact that partitioned tables do not support foreign keys (see - <xref linkend="partitioning-limitations"/>). + <xref + linkend="partitioning-limitations"/>). </para> </message> @@ -30988,10 +31123,11 @@ <para> Implicit versus explicit conversion of float to integer (such as inserting a float value into an integer column versus using - <function role="sql">CAST(... AS UNSIGNED)</function> before - inserting the value) could produce different results. Implicit - and explicit typecasts now are done the same way, with a value - equal to the nearest integer according to the prevailing + <function + role="sql">CAST(... AS UNSIGNED)</function> + before inserting the value) could produce different results. + Implicit and explicit typecasts now are done the same way, with + a value equal to the nearest integer according to the prevailing rounding mode. </para> @@ -31979,7 +32115,8 @@ <para> <literal>EXPLAIN SELECT</literal> now can be killed. See - <xref linkend="kill"/>. + <xref + linkend="kill"/>. </para> </message> @@ -32294,13 +32431,18 @@ Added <function role="capi">mysql_library_init()</function> and <function role="capi">mysql_library_end()</function> as synonyms for the <function role="capi">mysql_server_init()</function> and - <function role="capi">mysql_server_end()</function> C API - functions. <function role="capi">mysql_library_init()</function> - and <function role="capi">mysql_library_end()</function> are - <literal>#define</literal> symbols, but the names more clearly - indicate that they should be called when beginning and ending - use of a MySQL C API library no matter whether the application - uses <literal>libmysqlclient</literal> or + <function + role="capi">mysql_server_end()</function> C + API functions. + <function + role="capi">mysql_library_init()</function> + and + <function role="capi" + >mysql_library_end()</function> + are <literal>#define</literal> symbols, but the names more + clearly indicate that they should be called when beginning and + ending use of a MySQL C API library no matter whether the + application uses <literal>libmysqlclient</literal> or <literal>libmysqld</literal>. </para> @@ -32650,7 +32792,8 @@ <tags> <highlight type="incompatiblechange"/> <manual type="CURRENT_TIMESTAMP"/> - <manual type="TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP"/> + <manual + type="TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP"/> <manual type="UPDATE"/> <manual type="TIMESTAMP"/> <manual type="ON UPDATE CURRENT_TIMESTAMP"/> @@ -32990,7 +33133,8 @@ <para> A <literal>SELECT</literal> query which contained a - <function role="sql">GROUP_CONCAT()</function> and an + <function + role="sql">GROUP_CONCAT()</function> and an <literal>ORDER BY</literal> clause against the <literal>INFORMATION_SCHEMA</literal> resulted in an empty result set. @@ -33508,7 +33652,8 @@ <para> <function role="sql">UUID()</function> function implemented. Note that it does not work with replication yet. See - <xref linkend="miscellaneous-functions"/>. + <xref + linkend="miscellaneous-functions"/>. </para> </message> @@ -33562,7 +33707,8 @@ <para> Added <literal>WEEK</literal> and <literal>QUARTER</literal> values as <literal>INTERVAL</literal> arguments for the - <function role="sql">DATE_ADD()</function> and + <function role="sql" + >DATE_ADD()</function> and <function role="sql">DATE_SUB()</function> functions. </para> @@ -34773,7 +34919,8 @@ <para> The <literal>binlog_format</literal> system variable now is dynamic and can be changed at runtime, as described in - <xref linkend="replication-formats"/>. + <xref + linkend="replication-formats"/>. </para> </message> @@ -35561,7 +35708,8 @@ <para> For more information, see <literal> - <link linkend="mysql-cluster-param-ndbd-definition-timebetweenepochs">TimeBetweenEpochs</link> + <link linkend="mysql-cluster-param-ndbd-definition-timebetweenepochs" + >TimeBetweenEpochs</link> </literal>. </para> @@ -36412,8 +36560,9 @@ <para> If the second or third argument to - <function role="sqlop">BETWEEN</function> was a constant - expression such as <literal>'2005-09-01 - INTERVAL 6 + <function role="sqlop" + >BETWEEN</function> was a + constant expression such as <literal>'2005-09-01 - INTERVAL 6 MONTH</literal> and the other two arguments were columns, <function role="sqlop">BETWEEN</function> was evaluated incorrectly. @@ -36543,8 +36692,9 @@ <para> The <command>ndb_show_tables</command> utility now displays information about table events. See - <xref linkend="mysql-cluster-utilities-ndb-show-tables"/>, for - more information. + <xref + linkend="mysql-cluster-utilities-ndb-show-tables"/>, + for more information. </para> </message> @@ -36569,8 +36719,9 @@ Batching of updates on cluster replication slaves, enabled using the <option>--slave-allow-batching</option> option for <command>mysqld</command>. See - <xref linkend="mysql-cluster-replication-starting"/>, for more - information. + <xref + linkend="mysql-cluster-replication-starting"/>, + for more information. </para> </message> @@ -36936,9 +37087,10 @@ <para> For a <literal>DATE</literal> parameter sent via a <literal>MYSQL_TIME</literal> data structure, - <function role="capi">mysql_stmt_execute()</function> zeroed the - hour, minute, and second members of the structure rather than - treating them as read-only. + <function role="capi" + >mysql_stmt_execute()</function> + zeroed the hour, minute, and second members of the structure + rather than treating them as read-only. </para> </message> @@ -38013,7 +38165,8 @@ <para> An incorrect result was returned when comparing string values that were converted to <literal>TIME</literal> values with - <function role="sql">CAST()</function>. + <function + role="sql">CAST()</function>. </para> </message> @@ -38034,8 +38187,10 @@ <para> <function role="sql">CHAR(... USING ...)</function> and - <function role="sql">CONVERT(CHAR(...) USING ...)</function>, - though logically equivalent, could produce different results. + <function + role="sql">CONVERT(CHAR(...) USING + ...)</function>, though logically equivalent, could produce + different results. </para> </message> @@ -38231,8 +38386,9 @@ to cause the management client to provide status reports at regular intervals as well as for such reports to be written to the cluster log (depending on cluster event logging levels). See - <xref linkend="mysql-cluster-ndbd-definition"/>, for more - information about this parameter. + <xref + linkend="mysql-cluster-ndbd-definition"/>, for + more information about this parameter. </para> </message> @@ -39174,7 +39330,8 @@ <para> The <command>mysqld</command> Windows server was renamed to <command>mysqld-debug</command>. See - <xref linkend="windows-select-server"/>. + <xref + linkend="windows-select-server"/>. </para> </message> @@ -40822,12 +40979,13 @@ <para> For <literal>MyISAM</literal> tables, - <function role="sql">COUNT(*)</function> could return an - incorrect value if the <literal>WHERE</literal> clause compared - an indexed <literal>TEXT</literal> column to the empty string - (<literal>''</literal>). This happened if the column contained - empty strings and also strings starting with control characters - such as tab or newline. + <function role="sql" + >COUNT(*)</function> could return + an incorrect value if the <literal>WHERE</literal> clause + compared an indexed <literal>TEXT</literal> column to the empty + string (<literal>''</literal>). This happened if the column + contained empty strings and also strings starting with control + characters such as tab or newline. </para> </message> @@ -41162,8 +41320,9 @@ <para> The <function role="capi">mysql_next_result()</function> function could hang if you were executing many statements in a - <function role="capi">mysql_real_query()</function> call and one - of those statements raised an error. + <function + role="capi">mysql_real_query()</function> + call and one of those statements raised an error. </para> </message> @@ -41700,7 +41859,8 @@ System variables are now treated as having <literal>SYSVAR</literal> (system constant) coercibility. For example, <literal>@@version</literal> is now treated like - <function role="sql">VERSION()</function> and + <function role="sql" + >VERSION()</function> and <literal>@@character_set_client</literal> is now treated like <function role="sql">CHARSET( USER() )</function>. See <xref linkend="charset-collate-tricky"/>. @@ -41889,9 +42049,10 @@ <para> Easier replication upgrade (5.0.0 masters can read older binary logs and 5.0.0 slaves can read older relay logs). See - <xref linkend="replication-compatibility"/>, for more details). - The format of the binary log and relay log is changed compared - to that of MySQL 4.1 and older. + <xref + linkend="replication-compatibility"/>, for more + details). The format of the binary log and relay log is changed + compared to that of MySQL 4.1 and older. </para> </message> @@ -42321,8 +42482,9 @@ <para> On Windows, a definition for - <function role="capi">mysql_set_server_option()</function> was - missing from the C client library. + <function role="capi" + >mysql_set_server_option()</function> + was missing from the C client library. </para> </message> @@ -43349,7 +43511,8 @@ <para> <literal>UNHEX() IS NULL</literal> comparisons failed when - <function role="sql">UNHEX()</function> returned + <function + role="sql">UNHEX()</function> returned <literal>NULL</literal>. </para> @@ -43479,7 +43642,8 @@ <para> <literal>OPTIMIZE TABLE</literal> tried to sort R-tree indexes such as spatial indexes, although this is not possible (see - <xref linkend="optimize-table"/>). + <xref + linkend="optimize-table"/>). </para> </message> @@ -43507,7 +43671,8 @@ <para> Queries using an indexed column as the argument for the - <function role="sql">MIN()</function> and + <function + role="sql">MIN()</function> and <function role="sql">MAX()</function> functions following an <literal>ALTER TABLE .. DISABLE KEYS</literal> statement returned <errortext>Got error 124 from storage @@ -43988,7 +44153,8 @@ version of MySQL Server and repairs them if necessary. This program should be run for each MySQL upgrade (rather than <command>mysql_fix_privilege_tables</command>). See - <xref linkend="mysql-upgrade"/>. + <xref + linkend="mysql-upgrade"/>. </para> </listitem> @@ -44172,9 +44338,10 @@ <para> The test for the <literal>MYSQL_OPT_SSL_VERIFY_SERVER_CERT</literal> option for - <function role="capi">mysql_options()</function> was performed - incorrectly. Also changed as a result of this bugfix: The - <literal>arg</literal> option for the + <function + role="capi">mysql_options()</function> was + performed incorrectly. Also changed as a result of this bugfix: + The <literal>arg</literal> option for the <function role="capi">mysql_options()</function> C API function was changed from <literal>char *</literal> to <literal>void *</literal>. @@ -44383,15 +44550,18 @@ <para> The <function role="sql">MD5()</function>, - <function role="sql">SHA1()</function>, and + <function role="sql" + >SHA1()</function>, and <function role="sql">ENCRYPT()</function> functions should return a binary string, but the result sometimes was converted to the character set of the argument. - <function role="sql">MAKE_SET()</function> and - <function role="sql">EXPORT_SET()</function> now use the correct - character set for their default separators, resulting in - consistent result strings which can be coerced according to - normal character set rules. + <function role="sql" + >MAKE_SET()</function> and + <function role="sql" + >EXPORT_SET()</function> now use + the correct character set for their default separators, + resulting in consistent result strings which can be coerced + according to normal character set rules. </para> </message> @@ -44744,9 +44914,10 @@ <para> The character set was not being properly initialized for - <function role="sql">CAST()</function> with a type like - <literal>CHAR(2) BINARY</literal>, which resulted in incorrect - results or even a server crash. + <function + role="sql">CAST()</function> with a type + like <literal>CHAR(2) BINARY</literal>, which resulted in + incorrect results or even a server crash. </para> </message> @@ -44768,7 +44939,8 @@ <para> Added several <literal>InnoDB</literal> status variables. See - <xref linkend="server-status-variables"/>. + <xref + linkend="server-status-variables"/>. </para> </message> @@ -45233,7 +45405,8 @@ of ASCII sometimes was not done, resulting in <errortext>illegal mix of collations</errortext> errors. These cases now are resolved using repertoire, a new string expression attribute - (see <xref linkend="charset-repertoire"/>). + (see <xref + linkend="charset-repertoire"/>). </para> </message> @@ -45633,7 +45806,8 @@ <para> For more information, see - <xref linkend="replication-features-invoked"/>. + <xref + linkend="replication-features-invoked"/>. </para> </message> @@ -45688,7 +45862,8 @@ <para> The source distribution has been updated so that the UDF example can be compiled under Windows with CMake. See - <xref linkend="udf-compiling"/>. + <xref + linkend="udf-compiling"/>. </para> </message> @@ -46534,7 +46709,8 @@ <function role="sql">COUNT(DISTINCT <replaceable>col1</replaceable>, <replaceable>col2</replaceable>)</function> and - <function role="sql">COUNT(DISTINCT + <function role="sql" + >COUNT(DISTINCT CONCAT(<replaceable>col1</replaceable>, <replaceable>col2</replaceable>))</function> operations produced different results if one of the columns was an indexed @@ -47071,10 +47247,11 @@ <para> <function role="sql">DES_ENCRYPT()</function> and - <function role="sql">DES_DECRYPT()</function> require SSL - support to be enabled, but were not checking for it. Checking - for incorrect arguments or resource exhaustion was also improved - for these functions. + <function role="sql" + >DES_DECRYPT()</function> require + SSL support to be enabled, but were not checking for it. + Checking for incorrect arguments or resource exhaustion was also + improved for these functions. </para> </message> @@ -48814,8 +48991,9 @@ <para> Praparing a query using the - <function role="sql">CONVERT_TZ()</function> function with - constant arguments caused the server to crash. + <function role="sql" + >CONVERT_TZ()</function> function + with constant arguments caused the server to crash. </para> </message> @@ -48914,7 +49092,8 @@ <para> Using - <function role="sql">CONCAT(@<replaceable>user_var</replaceable>, + <function role="sql" + >CONCAT(@<replaceable>user_var</replaceable>, <replaceable>col_name</replaceable>)</function>, where <replaceable>col_name</replaceable> is a column in an <literal>INFORMATION_SCHEMA</literal> table, could cause @@ -49986,7 +50165,8 @@ Added configuration directives <literal>!include</literal> and <literal>!includedir</literal> for including option files and searching directories for option files. See - <xref linkend="option-files"/>, for usage. + <xref linkend="option-files" + />, for usage. </para> </message> @@ -50351,7 +50531,8 @@ column was a different size would cause <command>mysqld</command> to crash. For more information on replicating with different column definitions, see - <xref linkend="replication-features-differing-tables"/>. + <xref + linkend="replication-features-differing-tables"/>. </para> </message> @@ -50731,7 +50912,8 @@ the binary log index file, a warning is issued because MySQL falls back to using the hostname for that name, and this is prone to replication issues if the server's hostname's gets - changed later. See <xref linkend="open-bugs"/>. + changed later. See <xref + linkend="open-bugs"/>. </para> </message> @@ -50935,8 +51117,9 @@ <para> Additional issues remain with regard to the use of multi-byte character sets in MySQL Cluster Replication; see - <xref linkend="mysql-cluster-replication-issues"/>, for more - information. + <xref + linkend="mysql-cluster-replication-issues"/>, + for more information. </para> </message> @@ -51509,11 +51692,13 @@ <para> XPath expressions passed to the - <function role="sql">ExtractValue()</function> and - <function role="sql">UpdateXML()</function> functions can now - include the colon character (<quote> <literal>:</literal> - </quote>). This enables use of these functions with XML which - employs namespaces. + <function role="sql" + >ExtractValue()</function> and + <function role="sql" + >UpdateXML()</function> functions + can now include the colon character (<quote> + <literal>:</literal> </quote>). This enables use of these + functions with XML which employs namespaces. </para> </message> @@ -51541,8 +51726,9 @@ <para> The use of <function role="sql">MIN()</function> and - <function role="sql">MAX()</function> on columns with an index - prefix produced incorrect results in some queries. + <function + role="sql">MAX()</function> on columns with + an index prefix produced incorrect results in some queries. </para> </message> @@ -51882,15 +52068,17 @@ used, and applications written against the NDB API may need to be rewritten and recompiled to accomodate these changes. For more information about this change, see - <xref linkend="class-ndboperation-abortoption"/>. + <xref + linkend="class-ndboperation-abortoption"/>. </para> <para> This also affects the behavior of the <literal>NdbTransaction::execute()</literal> method, which now reports failure only if the transaction was actually aborted. - See <xref linkend="class-ndbtransaction-execute"/>, for more - information. + See <xref + linkend="class-ndbtransaction-execute"/>, + for more information. </para> </message> @@ -51930,7 +52118,8 @@ 5.0.10 or newer, you must drop all triggers and re-create them or <literal>DROP TRIGGER</literal> will not work after the upgrade. A suggested procedure for doing this is given in - <xref linkend="upgrading-from-4-1"/>. + <xref + linkend="upgrading-from-4-1"/>. </para> </note> @@ -52768,7 +52957,8 @@ <function role="sql">CAST(<replaceable>string_argument</replaceable> AS UNSIGNED)</function> didn't work for big integers above the signed range. Now this function and - <function role="sql">CAST(<replaceable>string_argument</replaceable> + <function role="sql" + >CAST(<replaceable>string_argument</replaceable> AS SIGNED)</function> also produces warnings for wrong string arguments. </para> @@ -53055,7 +53245,8 @@ You can now use the <literal>ndb_mgm_check_connection()</literal> function to determine whether a management server is running. See - <xref linkend="ndb-mgm-check-connection"/>. + <xref + linkend="ndb-mgm-check-connection"/>. </para> </message> @@ -53295,9 +53486,10 @@ <para> For a stored procedure defined with <literal>SQL SECURITY DEFINER</literal> characteristic, - <function role="sql">CURRENT_USER()</function> incorrectly - reported the use invoking the procedure, not the user who - defined it. + <function role="sql" + >CURRENT_USER()</function> + incorrectly reported the use invoking the procedure, not the + user who defined it. </para> </message> @@ -53455,8 +53647,9 @@ <para> Concatenating <function role="sql">USER()</function> or - <function role="sql">DATABASE()</function> with a column - produced invalid results. + <function + role="sql">DATABASE()</function> with a + column produced invalid results. </para> </message> @@ -53663,9 +53856,11 @@ <para> Added the - <function role="capi">mysql_set_local_infile_handler()</function> + <function role="capi" + >mysql_set_local_infile_handler()</function> and - <function role="capi">mysql_set_local_infile_default()</function> + <function role="capi" + >mysql_set_local_infile_default()</function> C API functions. </para> @@ -53771,7 +53966,8 @@ <para> Added new <literal>%f</literal> microseconds format specifier for <function role="sql">DATE_FORMAT()</function> and - <function role="sql">TIME_FORMAT()</function>. + <function role="sql" + >TIME_FORMAT()</function>. </para> </message> @@ -54455,8 +54651,9 @@ <para> Short-form IP addresses used as arguments to - <function role="sql">INET_ATON()</function> were not parsed - correctly. + <function role="sql" + >INET_ATON()</function> were not + parsed correctly. </para> </message> @@ -54643,8 +54840,9 @@ <para> A stored procedure that used - <function role="sql">LAST_INSERT_ID()</function> did not - replicate properly using statement-based binary logging. + <function role="sql" + >LAST_INSERT_ID()</function> did + not replicate properly using statement-based binary logging. </para> </message> @@ -55195,7 +55393,9 @@ <para> Support for <literal>%T, %r, %V, %v</literal> and <literal>%X, %x</literal> format specifiers was added to - <function role="sql">STR_TO_DATE()</function> function. + <function role="sql" + >STR_TO_DATE()</function> + function. </para> </message> @@ -55427,9 +55627,10 @@ <para> Calling the C API function - <function role="capi">mysql_stmt_fetch()</function> after all - rows of a result set were exhausted would return an error - instead of <literal>MYSQL_NO_DATA</literal>. + <function role="capi" + >mysql_stmt_fetch()</function> + after all rows of a result set were exhausted would return an + error instead of <literal>MYSQL_NO_DATA</literal>. </para> </message> @@ -55667,10 +55868,12 @@ <para> The <function role="sql">LEAST()</function> and - <function role="sql">GREATEST()</function> functions used to - return <literal>NULL</literal> only if all arguments were - <literal>NULL</literal>. Now they return <literal>NULL</literal> - if any argument is <literal>NULL</literal>, the same as Oracle. + <function + role="sql">GREATEST()</function> functions + used to return <literal>NULL</literal> only if all arguments + were <literal>NULL</literal>. Now they return + <literal>NULL</literal> if any argument is + <literal>NULL</literal>, the same as Oracle. </para> </message> @@ -55845,8 +56048,9 @@ <para> The <function role="sql">LEFT()</function> and - <function role="sql">RIGHT()</function> functions return - <literal>NULL</literal> if any argument is + <function role="sql" + >RIGHT()</function> functions + return <literal>NULL</literal> if any argument is <literal>NULL</literal>. </para> @@ -56032,7 +56236,9 @@ The syntax for <literal>CREATE TRIGGER</literal> now includes a <literal>DEFINER</literal> clause for specifying which access privileges to check at trigger invocation time. See - <xref linkend="create-trigger"/>, for more information. + <xref + linkend="create-trigger"/>, for more + information. </para> <formalpara> @@ -56939,7 +57145,8 @@ <para> Using the extended syntax for - <function role="sql">TRIM()</function> — that is, + <function role="sql" + >TRIM()</function> — that is, <function role="sql">TRIM(... FROM ...)</function> — in a <literal>SELECT</literal> statement defining a view caused an invalid syntax error when selecting from the view. @@ -57896,13 +58103,19 @@ <para> When used in view definitions, - <function role="sql">DAYNAME(<replaceable>expr</replaceable>)</function>, - <function role="sql">DAYOFWEEK(<replaceable>expr</replaceable>)</function>, - <function role="sql">WEEKDAY(<replaceable>expr</replaceable>)</function> + <function role="sql" + >DAYNAME(<replaceable>expr</replaceable>)</function>, + <function + role="sql">DAYOFWEEK(<replaceable>expr</replaceable>)</function>, + <function role="sql" + >WEEKDAY(<replaceable>expr</replaceable>)</function> were incorrectly treated as though the expression was - <function role="sql">TO_DAYS(<replaceable>expr</replaceable>)</function> + <function role="sql" + >TO_DAYS(<replaceable>expr</replaceable>)</function> or - <function role="sql">TO_DAYS(TO_DAYS(<replaceable>expr</replaceable>))</function>. + <function + role="sql" + >TO_DAYS(TO_DAYS(<replaceable>expr</replaceable>))</function>. </para> </message> @@ -58308,7 +58521,8 @@ <literal>ssl_cipher</literal>, and <literal>ssl_key</literal> system variables, which display the values given via the corresponding command options. See - <xref linkend="ssl-options"/>. + <xref + linkend="ssl-options"/>. </para> </message> @@ -58773,8 +58987,9 @@ <para> <function role="sql">MIN()</function> and - <function role="sql">MAX()</function> operations were not - optimized for views. + <function role="sql" + >MAX()</function> operations were + not optimized for views. </para> </message> @@ -59144,7 +59359,8 @@ proceed even if the option is necessarily ignored due to the absence of the plugin. (For a desecription of how <option>--loose</option> works, see - <xref linkend="command-line-options"/>.) + <xref + linkend="command-line-options"/>.) </para> </message> @@ -59274,7 +59490,8 @@ Added the <literal>old_mode</literal> system variable to cause the server to revert to certain behaviors present in older versions. Currently, this variable affects handling of index - hints. See <xref linkend="index-hints"/>. + hints. See <xref + linkend="index-hints"/>. </para> </message> @@ -59462,9 +59679,10 @@ <para> Queries containing subqueries with - <function role="sql">COUNT(*)</function> aggregated in an outer - context returned incorrect results. This happened only if the - subquery did not contain any references to outer columns. + <function role="sql" + >COUNT(*)</function> aggregated in + an outer context returned incorrect results. This happened only + if the subquery did not contain any references to outer columns. </para> </message> @@ -59579,8 +59797,9 @@ A problem with error handling when <literal>ndb_use_exact_count</literal> was enabled could lead to incorrect values returned from queries using - <function role="sql">COUNT()</function>. A warning is now - returned in such cases. + <function role="sql" + >COUNT()</function>. A warning is + now returned in such cases. </para> </message> @@ -59843,11 +60062,14 @@ <para> Lack of validation for input and output <literal>TIME</literal> values resulted in several problems: - <function role="sql">SEC_TO_TIME()</function> in some cases did - not clip large values to the <literal>TIME</literal> range - appropriately; <function role="sql">SEC_TO_TIME()</function> - treated <literal>BIGINT UNSIGNED</literal> values as signed; - only truncation warnings were produced when both truncation and + <function role="sql" + >SEC_TO_TIME()</function> in some + cases did not clip large values to the <literal>TIME</literal> + range appropriately; + <function role="sql" + >SEC_TO_TIME()</function> treated + <literal>BIGINT UNSIGNED</literal> values as signed; only + truncation warnings were produced when both truncation and out-of-range <literal>TIME</literal> values occurred. </para> @@ -61635,8 +61857,11 @@ <para> Added the <option>--sysdate-is-now</option> option to <command>mysqld</command> to enable - <function role="sql">SYSDATE()</function> to be treated as an - alias for <function role="sql">NOW()</function>. See + <function role="sql" + >SYSDATE()</function> to be treated + as an alias for + <function role="sql" + >NOW()</function>. See <xref linkend="date-and-time-functions"/>. </para> @@ -61746,9 +61971,10 @@ <function role="sqlop">BETWEEN</function> was a <literal>DATE</literal> or <literal>TIME</literal> column of a view and the other arguments were constants, - <function role="sqlop">BETWEEN</function> did not perform - conversion of the constants to the appropriate temporary type, - resulting in incorrect evaluation. + <function role="sqlop" + >BETWEEN</function> did not + perform conversion of the constants to the appropriate temporary + type, resulting in incorrect evaluation. </para> </message> @@ -62447,7 +62673,8 @@ <para> The <function role="sql">TIME_FORMAT()</function> function returned incorrect results with some format specifiers. See - <xref linkend="date-and-time-functions"/>. + <xref + linkend="date-and-time-functions"/>. </para> </message> @@ -62729,8 +62956,9 @@ <para> Performing an <function role="sqlop">IS NULL</function> check on the <function role="sql">MIN()</function> or - <function role="sql">MAX()</function> of an indexed column in a - complex query could produce incorrect results. + <function role="sql" + >MAX()</function> of an indexed + column in a complex query could produce incorrect results. </para> </message> @@ -63423,8 +63651,10 @@ <para> The combination of <function role="sql">COUNT()</function>, <literal>DISTINCT</literal>, and - <function role="sql">CONCAT()</function> sometimes triggered a - memory deallocation bug on Windows resulting in a server crash. + <function role="sql" + >CONCAT()</function> sometimes + triggered a memory deallocation bug on Windows resulting in a + server crash. </para> </message> @@ -63472,7 +63702,8 @@ <para> Basic support for stored procedures (SQL:2003 style). See - <xref linkend="stored-procedures"/>. + <xref + linkend="stored-procedures"/>. </para> </message> @@ -64182,7 +64413,8 @@ <para> The final character was omitted from the output of - <function role="sql">USER()</function>. + <function + role="sql">USER()</function>. </para> </message> @@ -64324,7 +64556,8 @@ <para> For more information, see - <xref linkend="mysql-cluster-utilities-ndb-size"/>. + <xref + linkend="mysql-cluster-utilities-ndb-size"/>. </para> </message> @@ -64828,7 +65061,8 @@ subqueries such as <literal>SELECT 1</literal> yielded incorrect results under certain circumstances due to incorrect application of - <function role="sql">MIN()</function>/<function role="sql">MAX()</function> + <function + role="sql">MIN()</function>/<function role="sql">MAX()</function> optimization. </para> @@ -64997,7 +65231,8 @@ is handled has changed. The pad value for inserts now is <literal>0x00</literal> rather than space, and there is no stripping of the pad value for selects. For details, see - <xref linkend="binary-varbinary"/>. + <xref + linkend="binary-varbinary"/>. </para> </message> @@ -65024,8 +65259,9 @@ <para> <literal>InnoDB</literal>: Enforce maximum - <function role="sql">CHAR_LENGTH()</function> of UTF-8 data in - <literal>ON UPDATE CASCADE</literal>. + <function role="sql" + >CHAR_LENGTH()</function> of + UTF-8 data in <literal>ON UPDATE CASCADE</literal>. </para> </message> @@ -65403,8 +65639,11 @@ <para> User variables and stored procedure variables are now supported for use in XPath expressions employed as arguments to the - <function role="sql">ExtractValue()</function> and - <function role="sql">UpdateXML()</function> functions. + <function + role="sql">ExtractValue()</function> and + <function role="sql" + >UpdateXML()</function> + functions. </para> <para> @@ -65716,9 +65955,11 @@ <para> A statement that produced a warning, when fetched via - <function role="capi">mysql_stmt_fetch()</function>, did not - produce a warning count according to - <function role="capi">mysql_warning_count()</function>. + <function + role="capi">mysql_stmt_fetch()</function>, + did not produce a warning count according to + <function role="capi" + >mysql_warning_count()</function>. </para> </message> @@ -66083,8 +66324,9 @@ <para> <literal/> API function - <function role="capi">mysql_stmt_prepare()</function> returned - wrong field length for TEXT columns. + <function role="capi" + >mysql_stmt_prepare()</function> + returned wrong field length for TEXT columns. </para> </message> @@ -66182,9 +66424,12 @@ <para> See - <link linkend="mysql-cluster-upgrade-downgrade-compatibility-online-add-drop-column">the + <link + linkend="mysql-cluster-upgrade-downgrade-compatibility-online-add-drop-column" + >the related note</link> in - <xref linkend="mysql-cluster-upgrade-downgrade-compatibility"/>, + <xref + linkend="mysql-cluster-upgrade-downgrade-compatibility"/>, for important information prior to upgrading a MySQL Cluster to MySQL 5.1.18 or later from MySQL 5.1.17 or earlier. </para> @@ -66340,9 +66585,10 @@ <para> The type of the value returned by the - <function role="sql">VARIANCE()</function> function varied - according to the type of the input value. The function should - always return a <literal>DOUBLE</literal> value. + <function role="sql" + >VARIANCE()</function> function + varied according to the type of the input value. The function + should always return a <literal>DOUBLE</literal> value. </para> </message> @@ -67130,7 +67376,8 @@ The <function role="sql">IN()</function> operator did not return correct results if all values in the list were constants and some of them used substring functions such as - <function role="sql">LEFT()</function>, + <function role="sql" + >LEFT()</function>, <function role="sql">RIGHT()</function>, or <function role="sql">MID()</function>. </para> @@ -67213,7 +67460,8 @@ <para> The optimizer did not take advantage of indexes on columns used for the second or third arguments of - <function role="sqlop">BETWEEN</function>. + <function role="sqlop" + >BETWEEN</function>. </para> </message> @@ -67408,11 +67656,12 @@ The MySQL server did not report any error if a statement (submitted through <function role="capi">mysql_real_query()</function> or - <function role="capi">mysql_stmt_prepare()</function>) was - terminated by garbage characters. This can happen if you pass a - wrong <literal>length</literal> parameter to these functions. - The result was that the garbage characters were written into the - binary log. + <function + role="capi">mysql_stmt_prepare()</function>) + was terminated by garbage characters. This can happen if you + pass a wrong <literal>length</literal> parameter to these + functions. The result was that the garbage characters were + written into the binary log. </para> </message> @@ -67440,9 +67689,10 @@ MySQL required explicit privileges on system time zone description tables for implicit access to them (that is, if one set the <literal>time_zone</literal> variable or used the - <function role="sql">CONVERT_TZ()</function> function) in cases - where some table-level or column-level privileges already - existed. + <function role="sql" + >CONVERT_TZ()</function> + function) in cases where some table-level or column-level + privileges already existed. </para> </message> @@ -67871,7 +68121,8 @@ </logentry> - <logentry entrytype="custom" customname="5.0.20aSSL" customtitle="Additional information about SSL support"> + <logentry entrytype="custom" customname="5.0.20aSSL" + customtitle="Additional information about SSL support"> <tags> <manual type="SSL"/> @@ -68010,7 +68261,9 @@ to be used when checking access privileges at routine invocation time if the routine has the <literal>SQL SECURITY DEFINER</literal> characteristic. See - <xref linkend="create-procedure"/>, for more information. + <xref + linkend="create-procedure"/>, for more + information. </para> <para> @@ -68974,8 +69227,9 @@ The <literal>ALL STATUS</literal> command in the cluster management client still displays status information for data nodes only. This is by design. See - <xref linkend="mysql-cluster-mgm-client-commands"/>, for more - information. + <xref + linkend="mysql-cluster-mgm-client-commands"/>, + for more information. </para> </note> @@ -69882,7 +70136,8 @@ A new configuration parameter <literal>TimeBetweenEpochsTimeout</literal> allows a timeout to be set for time between epochs. For more information, see - <xref linkend="mysql-cluster-ndbd-definition"/>. + <xref + linkend="mysql-cluster-ndbd-definition"/>. </para> </message> @@ -70078,7 +70333,8 @@ <para> The <literal>timezone</literal> system variable has been removed and replaced by <literal>system_time_zone</literal>. See - <xref linkend="server-system-variables"/>. + <xref + linkend="server-system-variables"/>. </para> </message> @@ -70209,9 +70465,13 @@ <para> Instances of the <function role="sql">VAR_SAMP()</function> function in view definitions were converted to - <function role="sql">VARIANCE()</function>. This is incorrect - because <function role="sql">VARIANCE()</function> is the same - as <function role="sql">VAR_POP()</function>, not + <function role="sql" + >VARIANCE()</function>. This is + incorrect because + <function role="sql" + >VARIANCE()</function> is the + same as <function role="sql" + >VAR_POP()</function>, not <function role="sql">VAR_SAMP()</function>. </para> @@ -70708,7 +70968,8 @@ <para> Character set conversion was not being done for - <function role="sql">FIND_IN_SET()</function>. + <function + role="sql">FIND_IN_SET()</function>. </para> </message> @@ -71351,7 +71612,8 @@ <para> Plugins now can have status variables that are displayed in the output from <literal>SHOW STATUS</literal>. See - <xref linkend="plugin-writing"/>. + <xref + linkend="plugin-writing"/>. </para> </message> @@ -71643,8 +71905,10 @@ New cluster management client <literal>DUMP</literal> commands were added to aid in tracking transactions, scan operations, and locks. See <xref linkend="ndb-internals-dump-command-2350"/>, - <xref linkend="ndb-internals-dump-command-2352"/>, and - <xref linkend="ndb-internals-dump-command-2550"/>. + <xref + linkend="ndb-internals-dump-command-2352"/>, and + <xref + linkend="ndb-internals-dump-command-2550"/>. </para> </message> @@ -71928,7 +72192,9 @@ The server could crash due to an attempt to allocate too much memory when <literal>GROUP BY <replaceable>blob_col</replaceable></literal> and - <function role="sql">COUNT(DISTINCT)</function> were used. + <function role="sql" + >COUNT(DISTINCT)</function> were + used. </para> </message> @@ -72145,8 +72411,10 @@ <para> Expressions involving nested - <function role="sql">CONCAT()</function> calls and character set - conversion of string constants could return an incorrect result. + <function role="sql" + >CONCAT()</function> calls and + character set conversion of string constants could return an + incorrect result. </para> </message> @@ -73967,7 +74235,8 @@ The <literal>ARCHIVE</literal> storage engine now supports the <literal>AUTO_INCREMENT</literal> column attribute and the <literal>AUTO_INCREMENT</literal> table option. - <xref linkend="archive-storage-engine"/>. + <xref + linkend="archive-storage-engine"/>. </para> </message> @@ -74588,7 +74857,8 @@ <para> For more information about this option, see - <xref linkend="mysql-cluster-options-variables"/>. + <xref + linkend="mysql-cluster-options-variables"/>. </para> </message> @@ -75555,7 +75825,9 @@ now requires a second argument. This is a source-level incompatibility that affects how you compile client programs; it does not affect the ability of compiled clients to communicate - with older servers. See <xref linkend="mysql-shutdown"/>. + with older servers. See + <xref + linkend="mysql-shutdown"/>. </para> </message> @@ -76268,8 +76540,9 @@ <para> After changing the character set with <literal>SET CHARACTER SET</literal>, the result of the - <function role="sql">GROUP_CONCAT()</function> function was not - converted to the proper character set. + <function role="sql" + >GROUP_CONCAT()</function> function + was not converted to the proper character set. </para> </message> @@ -76454,13 +76727,19 @@ <para> The bit operators - <function role="sqlop" condition="bitwise-or">|</function>, - <function role="sqlop" condition="bitwise-and">&</function>, - <function role="sqlop" condition="bitwise-xor">^</function>, - <function role="sqlop" condition="left-shift"><<</function>, - <function role="sqlop" condition="right-shift">>></function>, + <function role="sqlop" condition="bitwise-or" + >|</function>, + <function role="sqlop" condition="bitwise-and" + >&</function>, + <function role="sqlop" condition="bitwise-xor" + >^</function>, + <function role="sqlop" condition="left-shift" + ><<</function>, + <function role="sqlop" + condition="right-shift">>></function>, and - <function role="sqlop" condition="bitwise-invert">~</function>. + <function + role="sqlop" condition="bitwise-invert">~</function>. </para> </message> @@ -76616,7 +76895,8 @@ Added <option>--innodb-safe-binlog</option> server option, which adds consistency guarantees between the content of <literal>InnoDB</literal> tables and the binary log. See - <xref linkend="binary-log"/>. + <xref + linkend="binary-log"/>. </para> </message> @@ -76973,7 +77253,8 @@ <tbody> <row> <entry><emphasis role="bold">Deprecated / Obsolete</emphasis>:</entry> - <entry><emphasis role="bold">Current / Preferred</emphasis>:</entry> + <entry><emphasis role="bold">Current / + Preferred</emphasis>:</entry> </row> <row> <entry><literal>@@table_type</literal> @@ -77009,16 +77290,16 @@ <entry><literal>BACKUP TABLE</literal> </entry> - <entry><command>mysqldump</command>, <command>mysqlhotcopy</command>, or MySQL - Administrator</entry> + <entry><command>mysqldump</command>, + <command>mysqlhotcopy</command>, or MySQL Administrator</entry> </row> <row> <entry><literal>RESTORE TABLE</literal>, <literal>LOAD TABLE FROM MASTER</literal> </entry> - <entry><command>mysqldump</command>, <command>mysql</command>, or MySQL - Administrator</entry> + <entry><command>mysqldump</command>, <command>mysql</command>, or + MySQL Administrator</entry> </row> <row> <entry><literal>SHOW TABLE TYPES</literal> @@ -77045,7 +77326,8 @@ </entry> </row> <row> - <entry><literal>SHOW BDB LOGS</literal>, <literal>SHOW LOGS</literal> + <entry><literal>SHOW BDB LOGS</literal>, <literal>SHOW + LOGS</literal> </entry> <entry><literal>SHOW ENGINE BDB LOGS</literal> @@ -77170,16 +77452,16 @@ <entry><literal>BACKUP TABLE</literal> </entry> - <entry><command>mysqldump</command>, <command>mysqlhotcopy</command>, or MySQL - Administrator</entry> + <entry><command>mysqldump</command>, + <command>mysqlhotcopy</command>, or MySQL Administrator</entry> </row> <row> <entry><literal>RESTORE TABLE</literal>, <literal>LOAD TABLE FROM MASTER</literal> </entry> - <entry><command>mysqldump</command>, <command>mysql</command>, or MySQL - Administrator</entry> + <entry><command>mysqldump</command>, <command>mysql</command>, or + MySQL Administrator</entry> </row> <row> <entry><literal>SHOW TABLE TYPES</literal> @@ -77207,18 +77489,16 @@ </row> <row> <entry><option>--master-<replaceable>xxx</replaceable></option> -options to set replication parameters: - <option>--master-host</option>, - <option>--master-user</option>, - <option>--master-password </option>, - <option>--master-port</option>, - <option>--master-connect-retry</option>, - <option>--master-ssl</option>, - <option>--master-ssl-ca</option>, - <option>--master-ssl-capath</option>, - <option>--master-ssl-cert</option>, - <option>--master-ssl-cipher</option>, - <option>--master-ssl-key</option> + options to set replication parameters: + <option>--master-host</option>, <option>--master-user</option>, + <option>--master-password </option>, + <option>--master-port</option>, + <option>--master-connect-retry</option>, + <option>--master-ssl</option>, <option>--master-ssl-ca</option>, + <option>--master-ssl-capath</option>, + <option>--master-ssl-cert</option>, + <option>--master-ssl-cipher</option>, + <option>--master-ssl-key</option> </entry> <entry><literal>CHANGE MASTER</literal> @@ -77593,7 +77873,8 @@ <para> Add the <option>--defaults-group-suffix</option> option. See - <xref linkend="option-files"/>. + <xref + linkend="option-files"/>. </para> </message> @@ -77643,13 +77924,14 @@ <para> It was possible to provide the - <function role="sql">ExtractValue()</function> function with - input containing <quote>tags</quote> that were not valid XML; - for example, it was possible to use tag names beginning with a - digit, which are disallowed by the W3C's XML 1.0 specification. - Such cases caused the function to return <quote>junk</quote> - output rather than an error message signalling the user as to - the true nature of the problem. + <function role="sql" + >ExtractValue()</function> function + with input containing <quote>tags</quote> that were not valid + XML; for example, it was possible to use tag names beginning + with a digit, which are disallowed by the W3C's XML 1.0 + specification. Such cases caused the function to return + <quote>junk</quote> output rather than an error message + signalling the user as to the true nature of the problem. </para> </message> @@ -78332,7 +78614,8 @@ <para> Added support for <function role="sql">SUM(DISTINCT)</function>, <function role="sql">MIN(DISTINCT)</function>, and - <function role="sql">MAX(DISTINCT)</function>. + <function + role="sql">MAX(DISTINCT)</function>. </para> </message> @@ -78369,9 +78652,12 @@ <message> <para> - <function role="sqlop" condition="sounds-like"><replaceable>expr</replaceable> + <function role="sqlop" condition="sounds-like" + ><replaceable>expr</replaceable> SOUNDS LIKE <replaceable>expr</replaceable></function> same as - <function role="sql">SOUNDEX(<replaceable>expr</replaceable>)=SOUNDEX(<replaceable>expr</replaceable>)</function>. + <function + role="sql" + >SOUNDEX(<replaceable>expr</replaceable>)=SOUNDEX(<replaceable>expr</replaceable>)</function>. </para> </message> @@ -78460,8 +78746,9 @@ <function role="sql">RAND()</function> now allows non-constant initializers (such as a column name) as its argument. In this case, the seed is initialized with the value for each invocation - of <function role="sql">RAND()</function>. (One implication of - this is that for equal argument values, + of <function + role="sql">RAND()</function>. (One + implication of this is that for equal argument values, <function role="sql">RAND()</function> will return the same value each time.) </para> @@ -79318,7 +79605,8 @@ <filename>mysql_fix_privilege_tables.sql</filename> script that upgrades the grant tables to the current structure. Instructions for doing this are given in - <xref linkend="mysql-fix-privilege-tables"/>. + <xref linkend="mysql-fix-privilege-tables" + />. </para> </listitem> @@ -80729,8 +81017,9 @@ <para> The <literal>Ndb::startTransaction()</literal> method now provides an alternative interface for starting a transaction. - See <xref linkend="class-ndb-starttransaction"/>, for more - information. + See <xref + linkend="class-ndb-starttransaction"/>, for + more information. </para> </message> @@ -81366,10 +81655,11 @@ <para> Incorrect results could be returned for some queries that contained a select list expression with <literal>IN</literal> or - <function role="sqlop">BETWEEN</function> together with an - <literal>ORDER BY</literal> or <literal>GROUP BY</literal> on - the same expression using <literal>NOT IN</literal> or - <literal>NOT BETWEEN</literal>. + <function + role="sqlop">BETWEEN</function> together + with an <literal>ORDER BY</literal> or <literal>GROUP + BY</literal> on the same expression using <literal>NOT + IN</literal> or <literal>NOT BETWEEN</literal>. </para> </message> @@ -81590,8 +81880,9 @@ <para> Attempting to prepare a statement with - <function role="sql">RAND(?)</function> caused the server to - crash. + <function role="sql" + >RAND(?)</function> caused the + server to crash. </para> </message> @@ -81853,7 +82144,8 @@ possible to determine on a per-table basis whether or not an update to a given row on the master should be applied on the slave. For more information, see - <xref linkend="mysql-cluster-replication-conflict-resolution"/>. + <xref + linkend="mysql-cluster-replication-conflict-resolution"/>. </para> </message> @@ -82511,9 +82803,12 @@ if no rows were successfully inserted or changed. <quote>Not changed</quote> includes the case where a row was updated to its current values, but in that case, - <function role="sql">LAST_INSERT_ID()</function> should not be - reset to 0. Now <function role="sql">LAST_INSERT_ID()</function> - is reset to 0 only if no rows were successfully inserted or + <function role="sql" + >LAST_INSERT_ID()</function> should + not be reset to 0. Now + <function + role="sql">LAST_INSERT_ID()</function> is + reset to 0 only if no rows were successfully inserted or touched, whether or not touched rows were changed. </para> @@ -82650,18 +82945,23 @@ <para> The <function role="sql">CHARSET()</function>, - <function role="sql">COLLATION()</function>, and - <function role="sql">COERCIBILITY()</function> functions - sometimes returned <literal>NULL</literal>. + <function role="sql" + >COLLATION()</function>, and + <function role="sql" + >COERCIBILITY()</function> + functions sometimes returned <literal>NULL</literal>. <function role="sql">CHARSET()</function> and <function role="sql">COLLATION()</function> returned <literal>NULL</literal> when given any of these arguments that evaluated to <literal>NULL</literal>: A system function such as - <function role="sql">DATABASE()</function>; a column value; and - a user variable. Now <function role="sql">CHARSET()</function> - and <function role="sql">COLLATION()</function> return the - system character set and collation; the column character set and - collation; and <literal>binary</literal>. + <function + role="sql">DATABASE()</function>; a column + value; and a user variable. Now + <function role="sql">CHARSET()</function> and + <function role="sql" + >COLLATION()</function> return + the system character set and collation; the column character set + and collation; and <literal>binary</literal>. <function role="sql">COERCIBILITY(NULL)</function> now returns <quote>ignorable</quote> coercibility rather than <literal>NULL</literal>. @@ -83106,7 +83406,8 @@ <para> Naming a partition using the characters - <emphasis role="bold">Ç</emphasis> or + <emphasis role="bold" + >Ç</emphasis> or <emphasis role="bold">ç</emphasis> (<quote>c-cedilla</quote>; Unicode <literal>00C7</literal> or <literal>00E7</literal>) made unreadable the table containing the partition. @@ -83962,7 +84263,8 @@ OS-independent was the goal of this change.) Use <function role="sql">CONV()</function> to convert hexadecimal numbers to decimal. Example: - <function role="sql">CONV(MID('0x10',3),16,10)+0</function>. + <function role="sql" + >CONV(MID('0x10',3),16,10)+0</function>. </para> </message> @@ -84173,8 +84475,10 @@ <para> Executing a prepared statement with - <function role="sqlop" condition="between">BETWEEN ? AND - ?</function> and a datetime column caused the server to crash. + <function role="sqlop" + condition="between">BETWEEN ? + AND ?</function> and a datetime column caused the server to + crash. </para> </message> @@ -84478,8 +84782,9 @@ <para> Multiple invocations of the - <function role="sql">REVERSE()</function> function could return - different results. + <function role="sql" + >REVERSE()</function> function + could return different results. </para> </message> @@ -86470,10 +86775,11 @@ <para> Added the <option>--secure-file-priv</option> option for <command>mysqld</command>, which limits the effect of the - <function role="sql">LOAD_FILE()</function> function and the - <literal>LOAD DATA</literal> and <literal>SELECT ... INTO - OUTFILE</literal> statements to work only with files in a given - directory. + <function + role="sql">LOAD_FILE()</function> function + and the <literal>LOAD DATA</literal> and <literal>SELECT ... + INTO OUTFILE</literal> statements to work only with files in a + given directory. </para> </message> @@ -86793,7 +87099,8 @@ <para> Added new - <function role="sql">VARIANCE(<replaceable>expr</replaceable>)</function> + <function role="sql" + >VARIANCE(<replaceable>expr</replaceable>)</function> function returns the variance of <replaceable>expr</replaceable> </para> @@ -87356,8 +87663,9 @@ <para> Updating a field value when also requesting a lock with - <function role="sql">GET_LOCK()</function> would cause slave - servers in a replication environment to terminate. + <function + role="sql">GET_LOCK()</function> would cause + slave servers in a replication environment to terminate. </para> </message> @@ -87514,13 +87822,15 @@ <para> The coercibility for the return value of functions such as <function role="sql">USER()</function> or - <function role="sql">VERSION()</function> now is <quote>system - constant</quote> rather than <quote>implicit.</quote> This makes - these functions more coercible than column values so that - comparisons of the two do not result in <literal>Illegal mix of - collations</literal> errors. - <function role="sql">COERCIBILITY()</function> was modified to - accommodate this new coercibility value. See + <function role="sql" + >VERSION()</function> now is + <quote>system constant</quote> rather than + <quote>implicit.</quote> This makes these functions more + coercible than column values so that comparisons of the two do + not result in <literal>Illegal mix of collations</literal> + errors. <function + role="sql">COERCIBILITY()</function> + was modified to accommodate this new coercibility value. See <xref linkend="information-functions"/>. </para> @@ -87582,10 +87892,11 @@ <para> For a <literal>ucs2</literal> column, - <function role="sql">GROUP_CONCAT()</function> did not convert - separators to the result character set before inserting them, - producing a result containing a mixture of two different - character sets. + <function role="sql" + >GROUP_CONCAT()</function> did + not convert separators to the result character set before + inserting them, producing a result containing a mixture of two + different character sets. </para> </message> @@ -87711,7 +88022,8 @@ <para> <function role="sql">UNHEX()</function> function implemented. - See <xref linkend="string-functions"/>. + See <xref + linkend="string-functions"/>. </para> </message> @@ -87955,7 +88267,8 @@ specifies the locale that controls the language used to display day and month names and abbreviations. This variable affects the output from the <function role="sql">DATE_FORMAT()</function>, - <function role="sql">DAYNAME()</function> and + <function role="sql" + >DAYNAME()</function> and <function role="sql">MONTHNAME()</function> functions. See <xref linkend="locale-support"/>. </para> @@ -88230,10 +88543,14 @@ <para> <function role="sql">CURDATE()</function> is less than - <function role="sql">NOW()</function>, either when comparing - <function role="sql">CURDATE()</function> directly - (<literal>CURDATE() < NOW()</literal> is true) or when - casting <function role="sql">CURDATE()</function> to + <function + role="sql">NOW()</function>, either when + comparing <function + role="sql">CURDATE()</function> + directly (<literal>CURDATE() < NOW()</literal> is true) or + when casting + <function role="sql" + >CURDATE()</function> to <literal>DATE</literal> (<literal>CAST(CURDATE() AS DATE) < NOW()</literal> is true). However, storing <function role="sql">CURDATE()</function> in a @@ -88887,8 +89204,11 @@ <para> A memory leak occurred in the client library when a statement handle was freed on a closed connection (call to - <function role="capi">mysql_stmt_close()</function> after - <function role="capi">mysql_close()</function>). + <function role="capi" + >mysql_stmt_close()</function> + after + <function role="capi" + >mysql_close()</function>). </para> </message> @@ -90556,7 +90876,8 @@ <para> Invalid results were returned when - <function role="sql">CAST()</function> was applied to + <function role="sql" + >CAST()</function> was applied to <literal>NULL</literal> to obtain a signed or unsigned integer value. </para> @@ -92501,7 +92822,8 @@ <para> If <literal>STMT_ATTR_UPDATE_MAX_LENGTH</literal> is set for a prepared statement, - <function role="capi">mysql_stmt_store_result()</function> + <function role="capi" + >mysql_stmt_store_result()</function> updates <literal>field->max_length</literal> for numeric columns as well. </para> @@ -92546,7 +92868,8 @@ <para> It is now possible to replicate <literal>NDB</literal> tables having no explicit primary key. See - <xref linkend="mysql-cluster-replication"/>. + <xref + linkend="mysql-cluster-replication"/>. </para> </message> @@ -92947,7 +93270,9 @@ tables in the <literal>mysql</literal> database. If logging is enabled, either or both destinations can be selected. The <option>--log-output</option> option controls the destination or - destinations of log output. See <xref linkend="log-tables"/>. + destinations of log output. See + <xref + linkend="log-tables"/>. </para> <para> @@ -93707,7 +94032,8 @@ clause to be used for disambiguating whether the grant object is a table, a stored function, or a stored procedure. Use of this clause requires that you upgrade your grant tables. See - <xref linkend="mysql-fix-privilege-tables"/>. + <xref + linkend="mysql-fix-privilege-tables"/>. </para> </message> @@ -94215,7 +94541,8 @@ <para> You can now have only one log file group at any one time. See - <xref linkend="create-logfile-group"/>. + <xref + linkend="create-logfile-group"/>. </para> </message> @@ -94575,9 +94902,10 @@ As a result of this change, the <literal>MYSQL_OPT_READ_TIMEOUT</literal> and <literal>MYSQL_OPT_WRITE_TIMEOUT</literal> options for - <function role="capi">mysql_options()</function> now apply to - TCP/IP connections on all platforms. Previously, they applied - only to Windows. + <function + role="capi">mysql_options()</function> now + apply to TCP/IP connections on all platforms. Previously, they + applied only to Windows. </para> </message> @@ -94997,7 +95325,9 @@ <para> Added <function role="sql">TIMESTAMPADD()</function> and - <function role="sql">TIMESTAMPDIFF()</function> functions. + <function + role="sql">TIMESTAMPDIFF()</function> + functions. </para> </message> @@ -95150,8 +95480,9 @@ <para> New <function role="sql">CHARSET()</function> and - <function role="sql">COLLATION()</function> functions to return - the character set and collation of a string. + <function + role="sql">COLLATION()</function> functions + to return the character set and collation of a string. </para> </message> @@ -95486,7 +95817,8 @@ The <function role="sql">LOCATE()</function> function returned <literal>NULL</literal> if any of its arguments evaluated to <literal>NULL</literal>. Likewise, the predicate, - <function role="sql">LOCATE(<replaceable>str</replaceable>,NULL) + <function role="sql" + >LOCATE(<replaceable>str</replaceable>,NULL) IS NULL</function>, erroneously evaluated to <literal>FALSE</literal>. </para> @@ -95705,7 +96037,8 @@ before, which involves a minor incompatibility for multiple-row inserts that specify an explicit value for the auto-increment column in some but not all rows. See - <xref linkend="innodb-auto-increment-handling"/>. + <xref + linkend="innodb-auto-increment-handling"/>. </para> </message> @@ -95732,9 +96065,11 @@ Two new NDB API methods — <literal>aggregate()</literal> and <literal>validate()</literal> — were added to the <literal>NdbDictionary::Object::Table</literal> class. See - <xref linkend="class-table-aggregate"/>, and - <xref linkend="class-table-validate"/>, for more information. - This was done to rectify the following issues: + <xref + linkend="class-table-aggregate"/>, and + <xref + linkend="class-table-validate"/>, for more + information. This was done to rectify the following issues: <itemizedlist> <listitem> @@ -95861,7 +96196,8 @@ <para> For more information, see - <xref linkend="mysql-cluster-replication-schema"/>. + <xref + linkend="mysql-cluster-replication-schema"/>. </para> </message> @@ -96134,10 +96470,12 @@ <para> For the <function role="sql">IF()</function> and - <function role="sql">COALESCE()</function> function and - <function role="sqlop">CASE</function> expressions, large - unsigned integer values could be mishandled and result in - warnings. + <function + role="sql">COALESCE()</function> function + and <function role="sqlop" + >CASE</function> + expressions, large unsigned integer values could be mishandled + and result in warnings. </para> </message> @@ -96334,8 +96672,9 @@ <para> Following an invalid call to - <function role="sql">UpdateXML()</function>, calling the - function again (even if valid) crashed the server. + <function role="sql" + >UpdateXML()</function>, calling + the function again (even if valid) crashed the server. </para> </message> @@ -96609,7 +96948,9 @@ Whenever a TCP send buffer is over 80% full, temporary error 1218 (<errortext>Send Buffers overloaded in NDB kernel</errortext>) is now returned. See - <link linkend="mysql-cluster-param-tcp-definition-sendbuffermemory">SendBufferMemory</link> + <link + linkend="mysql-cluster-param-tcp-definition-sendbuffermemory" + >SendBufferMemory</link> for more information. </para> @@ -97291,10 +97632,11 @@ <para> The <function role="sql">LEAST()</function> and - <function role="sql">GREATEST()</function> functions compared - <literal>DATE</literal> and <literal>DATETIME</literal> values - as strings, which in some cases could lead to an incorrect - result. + <function + role="sql">GREATEST()</function> functions + compared <literal>DATE</literal> and <literal>DATETIME</literal> + values as strings, which in some cases could lead to an + incorrect result. </para> </message> @@ -97386,7 +97728,8 @@ Using aggregate functions in subqueries yielded incorrect results under certain circumstances due to incorrect application of - <function role="sql">MIN()</function>/<function role="sql">MAX()</function> + <function + role="sql">MIN()</function>/<function role="sql">MAX()</function> optimization. </para> @@ -97697,8 +98040,9 @@ reports at regular intervals as well as for such reports to be written to the cluster log (depending on cluster event logging levels). See - <xref linkend="mysql-cluster-ndbd-definition"/>, for more - information about this parameter. + <xref + linkend="mysql-cluster-ndbd-definition"/>, + for more information about this parameter. </para> </listitem> @@ -97711,7 +98055,8 @@ MemoryUsage</literal> reports the current data memory and index memory used by each data node. For more about the <literal>REPORT</literal> command, see - <xref linkend="mysql-cluster-mgm-client-commands"/>. + <xref + linkend="mysql-cluster-mgm-client-commands"/>. </para> </listitem> @@ -98542,7 +98887,8 @@ Added the <option>--innodb-safe-binlog</option> server option, which adds consistency guarantees between the content of <literal>InnoDB</literal> tables and the binary log. See - <xref linkend="binary-log"/>. + <xref + linkend="binary-log"/>. </para> </message> @@ -99082,11 +99428,12 @@ <para> During a call to - <function role="capi">mysql_change_user()</function>, when - authentication fails or the database to change to is unknown, a - subsequent call to any function that does network communication - leads to packets out of order. This problem was introduced in - MySQL 5.1.14. + <function role="capi" + >mysql_change_user()</function>, + when authentication fails or the database to change to is + unknown, a subsequent call to any function that does network + communication leads to packets out of order. This problem was + introduced in MySQL 5.1.14. </para> </message> @@ -99538,7 +99885,8 @@ <para> <function role="sql">FORMAT()</function> now performs better rounding for double values (for example, - <function role="sql">FORMAT(4.55,1)</function> returns + <function role="sql" + >FORMAT(4.55,1)</function> returns <literal>4.6</literal>, not <literal>4.5</literal>). </para> @@ -99838,9 +100186,11 @@ New cluster management client <literal>DUMP</literal> commands were added to aid in tracking transactions, scan operations, and locks. See <xref linkend="ndb-internals-dump-command-2350"/>, - <xref linkend="ndb-internals-dump-command-2352"/>, and - <xref linkend="ndb-internals-dump-command-2550"/>, for more - information. + <xref + linkend="ndb-internals-dump-command-2352"/>, and + <xref + linkend="ndb-internals-dump-command-2550"/>, for + more information. </para> </message> @@ -100816,7 +101166,8 @@ <para> A symlink vulnerability in the <command>mysqlaccess</command> script was reported by Javier Fernandez-Sanguino Pena and - <ulink url="http://www.debian.org/security/audit">Debian + <ulink + url="http://www.debian.org/security/audit">Debian Security Audit Team</ulink>. </para> @@ -101003,9 +101354,10 @@ <para> Comparison of <literal>TIME</literal> values using the - <function role="sqlop">BETWEEN</function> operator led to string - comparison, producing incorrect results in some cases. Now the - values are compared as integers. + <function + role="sqlop">BETWEEN</function> operator led + to string comparison, producing incorrect results in some cases. + Now the values are compared as integers. </para> </message> @@ -101394,7 +101746,8 @@ <para> <function role="sql">BIN()</function>, - <function role="sql">OCT()</function>, and + <function role="sql" + >OCT()</function>, and <function role="sql">CONV()</function> did not work with BIT values. </para> @@ -101570,7 +101923,8 @@ <para> Outer join elimination was erroneously applied for some queries that used a <literal>NOT BETWEEN</literal> condition, an - <function role="sql">IN(<replaceable>value_list</replaceable>)</function> + <function + role="sql">IN(<replaceable>value_list</replaceable>)</function> condition, or an <function role="sql">IF()</function> condition. </para> @@ -102154,9 +102508,11 @@ <para> The <function role="sql">LPAD()</function> and - <function role="sql">RPAD()</function> functions returned the - wrong length to - <function role="capi">mysql_fetch_fields()</function>. + <function role="sql" + >RPAD()</function> functions + returned the wrong length to + <function + role="capi">mysql_fetch_fields()</function>. </para> </message> @@ -102214,10 +102570,11 @@ <para> A <literal>HAVING</literal> clause that referred to - <function role="sql">RAND()</function> or a user-defined - function in the <literal>SELECT</literal> part of a query - through an alias could cause MySQL to crash or to return an - incorrect value. + <function + role="sql">RAND()</function> or a + user-defined function in the <literal>SELECT</literal> part of a + query through an alias could cause MySQL to crash or to return + an incorrect value. </para> </message> @@ -102264,8 +102621,9 @@ <para> For some values of the position argument, the - <function role="sql">INSERT()</function> function could insert a - NUL byte into the result. + <function role="sql" + >INSERT()</function> function + could insert a NUL byte into the result. </para> </message> @@ -103176,11 +103534,13 @@ <para> Within a trigger definition the - <function role="sql">CURRENT_USER()</function> function + <function role="sql" + >CURRENT_USER()</function> function evaluated to the user whose actions caused the trigger to be activated. Now that triggers have a <literal>DEFINER</literal> - value, <function role="sql">CURRENT_USER()</function> evaluates - to the trigger definer. + value, <function role="sql" + >CURRENT_USER()</function> + evaluates to the trigger definer. </para> </message> @@ -103294,10 +103654,11 @@ <para> In a multiple-row <literal>INSERT</literal> statement, - <function role="sql">LAST_INSERT_ID()</function> should return - the same value for each row. However, in some cases, the value - could change if the table being inserted into had its own - <literal>AUTO_INCREMENT</literal> column. + <function + role="sql">LAST_INSERT_ID()</function> + should return the same value for each row. However, in some + cases, the value could change if the table being inserted into + had its own <literal>AUTO_INCREMENT</literal> column. </para> </message> @@ -103483,7 +103844,9 @@ <para> <function role="capi">mysql_stmt_close()</function> hung when attempting to close a statement after failed - <function role="capi">mysql_stmt_fetch()</function> call. + <function role="capi" + >mysql_stmt_fetch()</function> + call. </para> </message> @@ -103933,7 +104296,8 @@ <literal>INFORMATION_SCHEMA.PROFILING</literal> table. Profiling is controlled via the <literal>profiling</literal> and <literal>profiling_history_size</literal> session variables. see - <xref linkend="show-profiles"/>, and + <xref + linkend="show-profiles"/>, and <xref linkend="profiling-table"/>. (From Jeremy Cole) </para> @@ -104181,7 +104545,8 @@ <para> A single cluster can now support up to 255 API nodes, including MySQL servers acting as SQL nodes. See - <xref linkend="mysql-cluster-limitations-exclusive-to-cluster"/>, + <xref + linkend="mysql-cluster-limitations-exclusive-to-cluster"/>, for more information. </para> @@ -104828,10 +105193,12 @@ <literal>mysql.func</literal> table and rejects those that contain directory pathname separator characters. (It already checked names as given in <literal>CREATE FUNCTION</literal> - statements.) See <xref linkend="udf-calling"/>, + statements.) See <xref + linkend="udf-calling"/>, <xref linkend="udf-aggr-calling"/>, and - <xref linkend="udf-security"/>. Thanks to Stefano Di Paola - <email>stefano.dipaola@stripped</email> for finding and + <xref + linkend="udf-security"/>. Thanks to Stefano Di + Paola <email>stefano.dipaola@stripped</email> for finding and informing us about this issue. </para> @@ -106086,7 +106453,8 @@ <para> Support for GIS (Geometrical data). See - <xref linkend="spatial-extensions"/>. + <xref + linkend="spatial-extensions"/>. </para> </message> @@ -106315,7 +106683,8 @@ The binary log file and binary log index file now behave like <literal>MyISAM</literal> when there is a "disk full" or "quota exceeded" error. See - <xref linkend="full-disk"/>. + <xref + linkend="full-disk"/>. </para> </message> @@ -107535,7 +107904,8 @@ <para> The <command>ndbd_redo_log_reader</command> utility is now part of the default build. For more information, see - <xref linkend="mysql-cluster-utilities-ndbd-redo-log-reader"/>. + <xref + linkend="mysql-cluster-utilities-ndbd-redo-log-reader"/>. </para> </message> @@ -107733,8 +108103,9 @@ RELEASE_LOCK()</literal> will not be written to the binary log anymore (this makes the binary log smaller); as a counterpart, the slave does not actually take the lock when it executes - <function role="sql">GET_LOCK()</function>. This is mainly an - optimization and should not affect existing setups. + <function role="sql" + >GET_LOCK()</function>. This is + mainly an optimization and should not affect existing setups. </para> </message> @@ -107762,8 +108133,9 @@ <para> Prepared statements containing - <function role="sql">CONNECTION_ID()</function> could be written - improperly to the binary log. + <function role="sql" + >CONNECTION_ID()</function> could + be written improperly to the binary log. </para> </message> @@ -107839,7 +108211,8 @@ <command>ndbd</command>, making it possible to skip specified nodes without waiting for them to start when starting the cluster. See - <xref linkend="mysql-cluster-ndbd-command-options"/>. + <xref + linkend="mysql-cluster-ndbd-command-options"/>. </para> </message> @@ -107887,7 +108260,8 @@ <para> Added the <literal>FEDERATED</literal> storage engine. See - <xref linkend="federated-storage-engine"/>. + <xref + linkend="federated-storage-engine"/>. </para> </message> @@ -108028,7 +108402,8 @@ <literal>Ndb_conflict_fn_old</literal> tracks the number of times that updates are prevented from being applied due to this type of conflict resolution. See - <xref linkend="mysql-cluster-replication-conflict-resolution"/>, + <xref + linkend="mysql-cluster-replication-conflict-resolution"/>, for more information. </para> @@ -108057,7 +108432,8 @@ predetermined percentages of memory allocation were given; setting this parameter allows for that behavior to be overridden. For more information, see - <xref linkend="mysql-cluster-ndbd-definition"/>. + <xref linkend="mysql-cluster-ndbd-definition" + />. </para> </message> @@ -109045,11 +109421,14 @@ <para> Added <function role="sql">VAR_POP()</function> and - <function role="sql">STDDEV_POP()</function> as standard SQL - aliases for the <function role="sql">VARIANCE()</function> and - <function role="sql">STDDEV()</function> functions that compute - population variance and standard deviation. Added new - <function role="sql">VAR_SAMP()</function> and + <function + role="sql">STDDEV_POP()</function> as + standard SQL aliases for the + <function role="sql">VARIANCE()</function> and + <function role="sql" + >STDDEV()</function> functions + that compute population variance and standard deviation. Added + new <function role="sql">VAR_SAMP()</function> and <function role="sql">STDDEV_SAMP()</function> functions to compute sample variance and standard deviation. </para> @@ -109461,8 +109840,10 @@ <para> Use of a <literal>CHAR</literal> or <literal>VARCHAR</literal> column with <function role="sql">MIN()</function> or - <function role="sql">MAX()</function> and <literal>GROUP BY ... - WITH ROLLUP</literal> caused the server to crash. + <function + role="sql">MAX()</function> and + <literal>GROUP BY ... WITH ROLLUP</literal> caused the server to + crash. </para> </message> @@ -109669,7 +110050,8 @@ New configuration directives <literal>!include</literal> and <literal>!includedir</literal> implemented for including option files and searching directories for option files. See - <xref linkend="option-files"/>, for usage. + <xref + linkend="option-files"/>, for usage. </para> </message> @@ -109818,7 +110200,8 @@ <para> <function role="sql">IN()</function> and - <function role="sql">CHAR()</function> can return + <function role="sql" + >CHAR()</function> can return <literal>NULL</literal>, but did not signal that to the query processor, causing incorrect results for <function role="sqlop" condition="is-null">IS NULL</function> @@ -111787,7 +112170,9 @@ Added support for read-only and updatable views based on a single table or other updatable views. View use requires that you upgrade your grant tables to add the view-related - privileges. See <xref linkend="mysql-fix-privilege-tables"/>. + privileges. See + <xref + linkend="mysql-fix-privilege-tables"/>. </para> </message> @@ -112346,7 +112731,9 @@ has also changed. This supercedes the functionality for replication from the master table to a slave table with more columns that was added in MySQL 5.1.12. For more information, - see <xref linkend="replication-features-differing-tables"/>. + see + <xref + linkend="replication-features-differing-tables"/>. </para> </message> @@ -112444,7 +112831,8 @@ <para> <function role="sql">MIN(<replaceable>col_name</replaceable>)</function> and - <function role="sql">MAX(<replaceable>col_name</replaceable>)</function> + <function role="sql" + >MAX(<replaceable>col_name</replaceable>)</function> could fail to produce the correct result if <replaceable>col_name</replaceable> was contained in multiple indexes and the optimizer did not choose the first index that @@ -112665,8 +113053,9 @@ <para> A call to <function role="sql">MIN()</function> with a - <function role="sqlop">CASE</function> expression as its - argument could return a non-minimum value. + <function + role="sqlop">CASE</function> expression as + its argument could return a non-minimum value. </para> </message> @@ -113005,8 +113394,9 @@ <para> Comparisons of <literal>DATE</literal> or <literal>DATETIME</literal> values for the - <function role="sql">IN()</function> function could yield - incorrect results. + <function role="sql" + >IN()</function> function could + yield incorrect results. </para> </message> @@ -113100,8 +113490,9 @@ An SQL-injection security hole has been found in multi-byte encoding processing. The bug was in the server, incorrectly parsing the string escaped with the - <function role="capi">mysql_real_escape_string()</function> C - API function. + <function role="capi" + >mysql_real_escape_string()</function> + C API function. </para> <para> @@ -113129,7 +113520,8 @@ to prevent SQL-injection attacks. It is impossible to fix this on the server side. The best solution is for applications to use character set-aware escaping offered by a function such - <function role="capi">mysql_real_escape_string()</function>. + <function role="capi" + >mysql_real_escape_string()</function>. </para> </formalpara> @@ -113139,8 +113531,9 @@ output of <function role="capi">mysql_real_escape_string()</function>. As a result, even when the character set-aware function - <function role="capi">mysql_real_escape_string()</function> was - used, SQL injection was possible. This bug has been fixed. + <function + role="capi">mysql_real_escape_string()</function> + was used, SQL injection was possible. This bug has been fixed. </para> <formalpara> @@ -113149,7 +113542,8 @@ <para> If you are unable to upgrade MySQL to a version that includes the fix for the bug in - <function role="capi">mysql_real_escape_string()</function> + <function role="capi" + >mysql_real_escape_string()</function> parsing, but run MySQL 5.0.1 or higher, you can use the <literal>NO_BACKSLASH_ESCAPES</literal> SQL mode as a workaround. (This mode was introduced in MySQL 5.0.1.) @@ -113734,7 +114128,8 @@ </para> <para> You can find - <link linkend="partitioning-limitations-functions">a + <link linkend="partitioning-limitations-functions" + >a complete list of these functions</link> under <citetitle>Partitioning Limitations</citetitle>. </para> @@ -113743,11 +114138,16 @@ <listitem> <para> The bit operators - <function role="sqlop" condition="bitwise-or">|</function>, - <function role="sqlop" condition="bitwise-and">&</function>, - <function role="sqlop" condition="bitwise-xor">^</function>, - <function role="sqlop" condition="left-shift"><<</function>, - <function role="sqlop" condition="right-shift">>></function>, + <function role="sqlop" condition="bitwise-or" + >|</function>, + <function role="sqlop" condition="bitwise-and" + >&</function>, + <function role="sqlop" + condition="bitwise-xor">^</function>, + <function role="sqlop" + condition="left-shift"><<</function>, + <function + role="sqlop" condition="right-shift">>></function>, and <function role="sqlop" condition="bitwise-invert">~</function>. </para> @@ -113785,7 +114185,8 @@ <para> For more information about these and other restrictions on partitioned tables in MySQL, see - <xref linkend="partitioning-limitations"/>. + <xref + linkend="partitioning-limitations"/>. </para> </message> @@ -113863,7 +114264,8 @@ Also, stored functions execute using the <literal>sql_mode</literal> value in force at function creation time rather than ignoring it. For more information, see - <xref linkend="create-procedure"/>. + <xref + linkend="create-procedure"/>. </para> </message> @@ -114452,8 +114854,9 @@ <para> For the embedded server, the - <function role="capi">mysql_stmt_store_result()</function> C API - function caused a memory leak for empty result sets. + <function role="capi" + >mysql_stmt_store_result()</function> + C API function caused a memory leak for empty result sets. </para> </message> @@ -114675,8 +115078,9 @@ <para> After an <literal>INSERT ... ON DUPLICATE KEY UPDATE</literal> statement that updated an existing row, - <function role="sql">LAST_INSERT_ID()</function> could return a - value not in the table. + <function role="sql" + >LAST_INSERT_ID()</function> + could return a value not in the table. </para> </message> @@ -114968,7 +115372,8 @@ <para> A <literal>WHERE</literal> clause that used - <function role="sqlop">BETWEEN</function> for + <function role="sqlop" + >BETWEEN</function> for <literal>DATETIME</literal> values could be treated differently for a <literal>SELECT</literal> and a view defined as that <literal>SELECT</literal>. @@ -115181,7 +115586,8 @@ <para> The data type for - <function role="sql">MAX(<replaceable>datetime_col</replaceable>)</function> + <function role="sql" + >MAX(<replaceable>datetime_col</replaceable>)</function> was returned as <literal>VARCHAR</literal> rather than <literal>DATETIME</literal> if the query included a <literal>GROUP BY</literal> clause. @@ -115201,8 +115607,9 @@ <para> Prepared statements using - <function role="sql">SUM(DISTINCT...)</function> did not perform - correctly. + <function role="sql" + >SUM(DISTINCT...)</function> did + not perform correctly. </para> </message> @@ -115241,7 +115648,9 @@ is usually set to 150 in the <filename>httpd.conf</filename> commonly distributed with Apache. For more information about <literal>MaxClient</literal>, see - <ulink url="http://httpd.apache.org/docs/2.2/mod/mpm_common.html#maxclients"/>.) + <ulink + url="http://httpd.apache.org/docs/2.2/mod/mpm_common.html#maxclients" + />.) </para> </message> @@ -115855,9 +116264,10 @@ <para> Calculation of <function role="sql">COUNT(DISTINCT)</function>, <function role="sql">AVG(DISTINCT)</function>, or - <function role="sql">SUM(DISTINCT)</function> when they are - referenced more than once in a single query with <literal>GROUP - BY</literal> could cause a server crash. + <function role="sql" + >SUM(DISTINCT)</function> when + they are referenced more than once in a single query with + <literal>GROUP BY</literal> could cause a server crash. </para> </message> @@ -116213,8 +116623,9 @@ <para> Creating a view that included the - <function role="sql">TIMESTAMPDIFF()</function> function - resulted in a invalid view. + <function role="sql" + >TIMESTAMPDIFF()</function> + function resulted in a invalid view. </para> </message> @@ -117039,8 +117450,9 @@ <para> Character set file parsing during - <function role="capi">mysql_real_connect()</function> read past - the end of a memory buffer. + <function role="capi" + >mysql_real_connect()</function> + read past the end of a memory buffer. </para> </message> @@ -117557,7 +117969,9 @@ to be used when checking access privileges at routine invocation time if the routine has the <literal>SQL SECURITY DEFINER</literal> characteristic. See - <xref linkend="create-procedure"/>, for more information. + <xref + linkend="create-procedure"/>, for more + information. </para> <para> @@ -117959,7 +118373,8 @@ caches. See <xref linkend="cache-index"/>. See <xref linkend="load-index"/>. Structured system variables are introduced as a means of grouping related key cache parameters. - See <xref linkend="structured-system-variables"/>. + See <xref + linkend="structured-system-variables"/>. </para> </message> @@ -118730,9 +119145,12 @@ <para> API change: the <literal>reconnect</literal> flag in the <literal>MYSQL</literal> structure is now set to 0 by - <function role="capi">mysql_real_connect()</function>. Only - those client programs which didn't explicitly set this flag to 0 - or 1 after <function role="capi">mysql_real_connect()</function> + <function + role="capi">mysql_real_connect()</function>. + Only those client programs which didn't explicitly set this flag + to 0 or 1 after + <function + role="capi">mysql_real_connect()</function> experience a change. Having automatic reconnection enabled by default was considered too dangerous (after reconnection, table locks, temporary tables, user and session variables are lost). @@ -118961,8 +119379,8 @@ <para> <literal>SHOW CREATE TABLE</literal> produced extraneous spaces - following the keywords <quote><literal>PRIMARY - KEY</literal></quote>. + following the keywords <quote> <literal>PRIMARY KEY</literal> + </quote>. </para> </message> @@ -119481,7 +119899,8 @@ <para> <function role="sql">BENCHMARK()</function>, - <function role="sql">ENCODE()</function>, + <function role="sql" + >ENCODE()</function>, <function role="sql">DECODE()</function>, and <function role="sql">FORMAT()</function> could only accept a constant for some parameters, and could not be used in prepared @@ -120332,7 +120751,8 @@ <para> Inserting the output of - <function role="sql">REPEAT('<replaceable>some_string</replaceable>', + <function role="sql" + >REPEAT('<replaceable>some_string</replaceable>', <replaceable>some_int</replaceable>)</function> into a <literal>BLOB</literal> column resulted in the error <errortext>Invalid blob attributes or invalid blob parts @@ -120383,8 +120803,9 @@ is created. In effect, different portions of a table are stored as separate tables in different locations, but from the user point of view, the partitioned table is still a single table. - See <xref linkend="partitioning"/>, for further information on - this functionality. (Author: Mikael Ronström) + See <xref + linkend="partitioning"/>, for further + information on this functionality. (Author: Mikael Ronström) </para> </message> @@ -121025,8 +121446,9 @@ <para> The result type of the - <function role="sql">GROUP_CONCAT()</function> function is now - <literal>VARCHAR</literal> only if the value of the + <function role="sql" + >GROUP_CONCAT()</function> function + is now <literal>VARCHAR</literal> only if the value of the <literal>group_concat_max_len</literal> system variable is less than or equal to 512. Otherwise, this function returns a <literal>BLOB</literal>. @@ -121408,8 +121830,9 @@ <para> When invoked within a view, - <function role="sql">SUBTIME()</function> returned incorrect - values. + <function role="sql" + >SUBTIME()</function> returned + incorrect values. </para> </message> @@ -121464,11 +121887,13 @@ implicit conversion to add a century was applied for date arithmetic performed with <function role="sql">DATE_ADD()</function>, - <function role="sql">DATE_SUB()</function>, <literal>+ + <function + role="sql">DATE_SUB()</function>, <literal>+ INTERVAL</literal>, and <literal>- INTERVAL</literal>. (For - example, <function role="sql">DATE_ADD('0050-01-01 00:00:00', - INTERVAL 0 SECOND)</function> became <literal>'2050-01-01 - 00:00:00'</literal>.) + example, <function role="sql" + >DATE_ADD('0050-01-01 + 00:00:00', INTERVAL 0 SECOND)</function> became + <literal>'2050-01-01 00:00:00'</literal>.) </para> </message> @@ -121479,9 +121904,12 @@ For dates with 4-digit year parts less than 200, an implicit conversion to add a century was applied for date arithmetic performed with <function role="sql">DATE_ADD()</function>, - <function role="sql">DATE_SUB()</function>, <literal>+ - INTERVAL</literal>, and <literal>- INTERVAL</literal>. (For - example, <function role="sql">DATE_ADD('0050-01-01 00:00:00', + <function role="sql" + >DATE_SUB()</function>, + <literal>+ INTERVAL</literal>, and <literal>- + INTERVAL</literal>. (For example, + <function role="sql" + >DATE_ADD('0050-01-01 00:00:00', INTERVAL 0 SECOND)</function> became <literal>'2050-01-01 00:00:00'</literal>.) Now these operations return <literal>NULL</literal> rather than an incorrect @@ -121923,10 +122351,12 @@ <para> Basic time zone conversion function - <function role="sql">CONVERT_TZ()</function> was added. It - assumes that its first argument is a datetime value in the time - zone specified by its second argument and returns the equivalent - datetime value in the time zone specified by its third argument. + <function role="sql" + >CONVERT_TZ()</function> was + added. It assumes that its first argument is a datetime value in + the time zone specified by its second argument and returns the + equivalent datetime value in the time zone specified by its + third argument. </para> </message> @@ -122805,7 +123235,8 @@ <para> Added - <function role="capi">mysql_get_character_set_info()</function> + <function role="capi" + >mysql_get_character_set_info()</function> C API function for obtaining information about the default character set of the current connection. </para> @@ -123450,7 +123881,8 @@ <message> <para> - <function role="sql">AES_DECRYPT(<replaceable>col_name</replaceable>,<replaceable>key</replaceable>)</function> + <function role="sql" + >AES_DECRYPT(<replaceable>col_name</replaceable>,<replaceable>key</replaceable>)</function> could fail to return <literal>NULL</literal> for invalid values in <replaceable>col_name</replaceable>, if <replaceable>col_name</replaceable> was declared as <literal>NOT @@ -123667,7 +124099,8 @@ <para> A call to - <function role="capi">mysql_stmt_store_result()</function> + <function role="capi" + >mysql_stmt_store_result()</function> occurred without a preceding call to <function role="capi">mysql_stmt_bind_result()</function> caused the server to crash. @@ -123719,7 +124152,8 @@ <message> <para> - <function role="sql">COUNT(<replaceable>decimal_expr</replaceable>)</function> + <function role="sql" + >COUNT(<replaceable>decimal_expr</replaceable>)</function> sometimes generated a spurious truncation warning. </para> @@ -123848,7 +124282,8 @@ <para> Examples: <filename>mysql-essential-4.1.9-win32.msi</filename>, <filename>mysql-noinstall-4.1.9-win32.zip</filename> See - <xref linkend="windows-installation"/>. + <xref + linkend="windows-installation"/>. </para> </message> @@ -124061,7 +124496,8 @@ <message> <para> - <function role="capi">mysql_options(...,MYSQL_OPT_LOCAL_INFILE,...)</function> + <function role="capi" + >mysql_options(...,MYSQL_OPT_LOCAL_INFILE,...)</function> failed to disable <literal>LOAD DATA LOCAL INFILE</literal>. </para> @@ -124153,9 +124589,9 @@ reads. This could also lead to character data having the wrong lettercase in the backup if such a column was updated during the backup; for example, supposing that the column used - <literal>latin_ci</literal>, then - <quote><literal>aAa</literal></quote> might be stored in the - backup as <quote><literal>AAA</literal></quote>. + <literal>latin_ci</literal>, then <quote> <literal>aAa</literal> + </quote> might be stored in the backup as <quote> + <literal>AAA</literal> </quote>. </para> </message> @@ -124182,7 +124618,8 @@ <command>mysqld</command> wait a specified amount of time to be connected to the cluster before accepting client connections. See - <link linkend="option_mysqld_ndb_wait_connected">here</link>, + <link linkend="option_mysqld_ndb_wait_connected" + >here</link>, for more information. </para> @@ -124349,14 +124786,16 @@ from MySQL 5.1.17 or earlier for a replication slave cluster; you must shut down all SQL nodes as part of the upgrade procedure. See - <xref linkend="mysql-cluster-upgrade-downgrade-compatibility"/> + <xref + linkend="mysql-cluster-upgrade-downgrade-compatibility"/> before upgrading for details. </para> <para> For more information about the changes to <literal>mysql.ndb_apply_status</literal> see - <xref linkend="mysql-cluster-replication-schema"/>. + <xref + linkend="mysql-cluster-replication-schema"/>. </para> </message> @@ -124652,7 +125091,8 @@ <para> It is no longer possible to issue <literal>FLUSH</literal> commands from within stored functions or triggers. See - <xref linkend="routine-restrictions"/>, for details. + <xref + linkend="routine-restrictions"/>, for details. </para> </message> @@ -125071,7 +125511,7 @@ rows yielded incorrect results under certain circumstances due to incorrect application of <function role="sql">MIN()</function>/<function -role="sql">MAX()</function> + role="sql">MAX()</function> optimization. </para> @@ -125136,8 +125576,11 @@ <para> On Windows, an application that called - <function role="capi">mysql_thread_init()</function> but forgot - to call <function role="capi">mysql_thread_end()</function> + <function role="capi" + >mysql_thread_init()</function> + but forgot to call + <function + role="capi">mysql_thread_end()</function> would get this error: <errortext>Error in my_thread_global_end()</errortext>. </para> @@ -125240,7 +125683,8 @@ <para> The <literal>binlog_format</literal> system variable now can be set to a third format, <literal>MIXED</literal>, as described in - <xref linkend="replication-formats"/>. + <xref + linkend="replication-formats"/>. </para> </message> @@ -125831,7 +126275,8 @@ <para> The syntax - <function role="sql">CONVERT(<replaceable>expr</replaceable>,<replaceable>type</replaceable>)</function> + <function role="sql" + >CONVERT(<replaceable>expr</replaceable>,<replaceable>type</replaceable>)</function> is now supported again. </para> @@ -125922,7 +126367,9 @@ <function role="sql">LAST_INSERT_ID()</function>, because the side effects of inserting default values into columns not part of the view should not be visible. MySQL was incorrectly setting - <function role="sql">LAST_INSERT_ID()</function> to zero. + <function + role="sql">LAST_INSERT_ID()</function> to + zero. </para> </message> @@ -126104,10 +126551,11 @@ <para> <function role="sql">NOW()</function>, - <function role="sql">CURRENT_TIME()</function> and values - generated by timestamp columns are now constant for the duration - of a stored function or trigger. This prevents the breaking of - statements-based replication. + <function role="sql" + >CURRENT_TIME()</function> and + values generated by timestamp columns are now constant for the + duration of a stored function or trigger. This prevents the + breaking of statements-based replication. </para> </message> @@ -126209,7 +126657,8 @@ <para> Duplicates were not properly identified among (potentially) long strings used as arguments for - <function role="sql">GROUP_CONCAT(DISTINCT)</function>. + <function role="sql" + >GROUP_CONCAT(DISTINCT)</function>. </para> </message> @@ -126522,8 +126971,9 @@ <para> Multiple-table <literal>UPDATE</literal> queries using - <function role="sql">CONVERT_TZ()</function> would fail with an - error. + <function + role="sql">CONVERT_TZ()</function> would + fail with an error. </para> </message> @@ -127406,8 +127856,9 @@ <para> If query execution involved a temporary table, - <function role="sql">GROUP_CONCAT()</function> could return a - result with an incorrect character set. + <function role="sql" + >GROUP_CONCAT()</function> could + return a result with an incorrect character set. </para> </message> @@ -127488,8 +127939,9 @@ <para> <literal>ORDER BY DESC</literal> within the - <function role="sql">GROUP_CONCAT()</function> function was not - honored when used in a view. + <function role="sql" + >GROUP_CONCAT()</function> + function was not honored when used in a view. </para> </message> @@ -128048,7 +128500,8 @@ <para> The <literal>INFORMATION_SCHEMA</literal> database now includes a <literal>TRIGGERS</literal> table. See - <xref linkend="triggers-table"/>, for details. + <xref + linkend="triggers-table"/>, for details. </para> </listitem> @@ -128117,7 +128570,8 @@ <para> Allow - <function role="sql">DEFAULT(<replaceable>col_name</replaceable>)</function> + <function role="sql" + >DEFAULT(<replaceable>col_name</replaceable>)</function> in expressions; it produces the column's default value. </para> @@ -128993,11 +129447,15 @@ <para> Under certain circumstances, - <function role="sql">AVG(<replaceable>key_val</replaceable>)</function> + <function role="sql" + >AVG(<replaceable>key_val</replaceable>)</function> returned a value but - <function role="sql">MAX(<replaceable>key_val</replaceable>)</function> + <function role="sql" + >MAX(<replaceable>key_val</replaceable>)</function> returned an empty set due to incorrect application of - <function role="sql">MIN()/MAX()</function> optimization. + <function role="sql" + >MIN()/MAX()</function> + optimization. </para> </message> @@ -129391,8 +129849,9 @@ <para> The C API function - <function role="capi">mysql_stmt_reset()</function> did not - clear error information. + <function role="capi" + >mysql_stmt_reset()</function> did + not clear error information. </para> </message> @@ -129459,7 +129918,9 @@ that <literal>FLUSH LOGS</literal>, <literal>FLUSH MASTER</literal>, <literal>FLUSH SLAVE</literal>, and <literal>FLUSH TABLES WITH READ LOCK</literal> are not logged in - any case. For a syntax example, see <xref linkend="flush"/>. + any case. For a syntax example, see + <xref linkend="flush" + />. </para> </message> @@ -129574,8 +130035,9 @@ <para> <function role="capi">mysql_affected_rows()</function> could return values different from - <function role="capi">mysql_stmt_affected_rows()</function> for - the same sequence of statements. + <function role="capi" + >mysql_stmt_affected_rows()</function> + for the same sequence of statements. </para> </message> @@ -130979,8 +131441,9 @@ The server now issues a warning to the error log when it encounters older tables that contain character columns that might be interpreted by newer servers to have a different column - length. See <xref linkend="upgrading-from-4-0"/>, for a - discussion of this problem and what to do about it. + length. See <xref + linkend="upgrading-from-4-0"/>, for + a discussion of this problem and what to do about it. </para> </message> @@ -131305,7 +131768,8 @@ <para> Queries that combined <literal>SELECT DISTINCT</literal>, - <function role="sql">SUM()</function>, and + <function + role="sql">SUM()</function>, and <literal>ROLLUP</literal> could cause the MySQL server to crash. </para> @@ -132071,9 +132535,11 @@ <para> <function role="sql">MIN()</function> and - <function role="sql">MAX()</function> sometimes returned a - non-<literal>NULL</literal> value for an empty row set (for - example, <literal>SELECT MAX(1) FROM empty_table</literal>). + <function role="sql" + >MAX()</function> sometimes + returned a non-<literal>NULL</literal> value for an empty row + set (for example, <literal>SELECT MAX(1) FROM + empty_table</literal>). </para> </message> @@ -135213,7 +135679,8 @@ <para> The <literal>Aborted_clients</literal> status variable was incremented twice if a client exited without calling - <function role="capi">mysql_close()</function>. + <function + role="capi">mysql_close()</function>. </para> </message> @@ -135554,10 +136021,12 @@ NAME</literal>. The <literal>RENAME DATABASE</literal> statement was intended for upgrading database directory names to the encoding format used in 5.1 for representing identifiers in the - filesystem (see <xref linkend="identifier-mapping"/>). However, - the statement was found to be dangerous because it could result - in loss of database contents. See - <xref linkend="rename-database"/> and + filesystem (see <xref linkend="identifier-mapping" + />). + However, the statement was found to be dangerous because it + could result in loss of database contents. See + <xref linkend="rename-database" + /> and <xref linkend="alter-database"/>. </para> @@ -136253,7 +136722,9 @@ <para> The <function role="capi">mysql_change_user()</function> C API function caused advisory locks (obtained with - <function role="sql">GET_LOCK()</function>) to malfunction. + <function role="sql" + >GET_LOCK()</function>) to + malfunction. </para> </message> @@ -136557,8 +137028,9 @@ <para> Use of <literal>DECIMAL(<replaceable>n</replaceable>, <replaceable>n</replaceable>) ZEROFILL</literal> in - <function role="sql">GROUP_CONCAT()</function> could cause a - server crash. + <function + role="sql">GROUP_CONCAT()</function> could + cause a server crash. </para> </message> @@ -137065,9 +137537,10 @@ <para> The length of the result from - <function role="sql">IFNULL()</function> could be calculated - incorrectly because the sign of the result was not taken into - account. + <function role="sql" + >IFNULL()</function> could be + calculated incorrectly because the sign of the result was not + taken into account. </para> </message> @@ -137235,8 +137708,9 @@ <para> The result from - <function role="sql">CHAR(<replaceable>str</replaceable> USING - ucs2</function>) did not add a leading 0x00 byte for input + <function role="sql" + >CHAR(<replaceable>str</replaceable> + USING ucs2</function>) did not add a leading 0x00 byte for input strings with an odd number of bytes. </para> @@ -137623,15 +138097,19 @@ Several type-preserving functions and operators returned an incorrect result type that does not match their argument types: <function role="sql">COALESCE()</function>, - <function role="sql">IF()</function>, + <function role="sql" + >IF()</function>, <function role="sql">IFNULL()</function>, - <function role="sql">LEAST()</function>, - <function role="sql">GREATEST()</function>, + <function + role="sql">LEAST()</function>, + <function role="sql" + >GREATEST()</function>, <function role="sqlop">CASE</function>. These now aggregate using the precise SQL types of their arguments rather than the internal type. In addition, the result type of the - <function role="sql">STR_TO_DATE()</function> function is now - <literal>DATETIME</literal> by default. + <function + role="sql">STR_TO_DATE()</function> function + is now <literal>DATETIME</literal> by default. </para> </message> @@ -137919,8 +138397,10 @@ <para> When invoked with constant arguments, - <function role="sql">STR_TO_DATE()</function> could use a cached - value for the format string and return incorrect results. + <function role="sql" + >STR_TO_DATE()</function> could + use a cached value for the format string and return incorrect + results. </para> </message> @@ -139171,9 +139651,10 @@ <para> Using the <function role="sql">MIN()</function> or - <function role="sql">MAX()</function> function to select one - part of a multi-part key could cause a crash when the function - result was <literal>NULL</literal>. + <function + role="sql">MAX()</function> function to + select one part of a multi-part key could cause a crash when the + function result was <literal>NULL</literal>. </para> </message> @@ -139725,9 +140206,11 @@ <para> The server could crash during <literal>filesort</literal> for <literal>ORDER BY</literal> based on expressions with - <function role="sql">INET_NTOA()</function> or - <function role="sql">OCT()</function> if those functions - returned <literal>NULL</literal>. + <function + role="sql">INET_NTOA()</function> or + <function role="sql" + >OCT()</function> if those + functions returned <literal>NULL</literal>. </para> </message> @@ -139755,14 +140238,19 @@ <para> Comparison results for <function role="sqlop">BETWEEN</function> were different from those for operators like - <function role="sqlop" condition="less-than"><</function> and - <function role="sqlop" condition="greater-than">></function> + <function role="sqlop" + condition="less-than"><</function> + and + <function role="sqlop" + condition="greater-than">></function> for <literal>DATETIME</literal>-like values with trailing extra characters such as <literal>'2007-10-01 00:00:00 - GMT-6'</literal>. <function role="sqlop">BETWEEN</function> - treated the values as <literal>DATETIME</literal>, whereas the - other operators performed a binary-string comparison. Now they - all uniformly use a <literal>DATETIME</literal> comparison, but + GMT-6'</literal>. + <function + role="sqlop">BETWEEN</function> treated the + values as <literal>DATETIME</literal>, whereas the other + operators performed a binary-string comparison. Now they all + uniformly use a <literal>DATETIME</literal> comparison, but generate warnings for values with trailing garbage. </para> @@ -139940,6 +140428,4 @@ </logentry> -<!-- WL#4169 EDITS START HERE --> - </changelog>
| Thread | ||
|---|---|---|
| • svn commit - mysqldoc@docsrva: r11409 - trunk/dynamic-docs/changelog | jon | 29 Jul |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 5.210 sec. using MySQL 5.1.14-beta-log