From: Date: January 9 2008 8:14pm Subject: svn commit - mysqldoc@docsrva: r9535 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-6.0 refman-common List-Archive: http://lists.mysql.com/commits/40784 Message-Id: <200801091914.m09JEe1K019933@docsrva.mysql.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Author: paul Date: 2008-01-09 20:14:38 +0100 (Wed, 09 Jan 2008) New Revision: 9535 Log: r34798@arctic: paul | 2008-01-09 11:20:11 -0600 Add markup. Modified: trunk/refman-4.1/data-types.xml trunk/refman-4.1/dba-core.xml trunk/refman-4.1/errors-problems.xml trunk/refman-4.1/functions-core.xml trunk/refman-4.1/internationalization.xml trunk/refman-4.1/introduction.xml trunk/refman-4.1/language-structure.xml trunk/refman-4.1/restrictions.xml trunk/refman-4.1/sql-syntax.xml trunk/refman-4.1/tutorial.xml trunk/refman-5.0/data-types.xml trunk/refman-5.0/dba-core.xml trunk/refman-5.0/errors-problems.xml trunk/refman-5.0/faqs.xml trunk/refman-5.0/functions-core.xml trunk/refman-5.0/information-schema.xml trunk/refman-5.0/internationalization.xml trunk/refman-5.0/introduction.xml trunk/refman-5.0/language-structure-core.xml trunk/refman-5.0/replication-configuration.xml trunk/refman-5.0/restrictions.xml trunk/refman-5.0/sql-syntax.xml trunk/refman-5.0/tutorial.xml trunk/refman-5.1/ccsg-temp.xml trunk/refman-5.1/data-types.xml trunk/refman-5.1/dba-core-new-tmp.xml trunk/refman-5.1/dba-core.xml trunk/refman-5.1/errors-problems-core.xml trunk/refman-5.1/faqs.xml trunk/refman-5.1/functions-core.xml trunk/refman-5.1/information-schema.xml trunk/refman-5.1/internationalization.xml trunk/refman-5.1/introduction.xml trunk/refman-5.1/language-structure-core.xml trunk/refman-5.1/mysql-cluster-ccsg-merge-temp.xml trunk/refman-5.1/mysql-cluster-management.xml trunk/refman-5.1/partitioning-guide.xml trunk/refman-5.1/replication-configuration.xml trunk/refman-5.1/restrictions.xml trunk/refman-5.1/sql-syntax.xml trunk/refman-5.1/tutorial.xml trunk/refman-6.0/data-types.xml trunk/refman-6.0/dba-core.xml trunk/refman-6.0/errors-problems.xml trunk/refman-6.0/faqs.xml trunk/refman-6.0/functions-core.xml trunk/refman-6.0/information-schema.xml trunk/refman-6.0/internationalization.xml trunk/refman-6.0/introduction.xml trunk/refman-6.0/language-structure-core.xml trunk/refman-6.0/mysql-cluster-management.xml trunk/refman-6.0/partitioning-guide.xml trunk/refman-6.0/replication-configuration.xml trunk/refman-6.0/restrictions.xml trunk/refman-6.0/sql-syntax.xml trunk/refman-6.0/tutorial.xml trunk/refman-common/news-innodb.xml Property changes on: trunk ___________________________________________________________________ Name: svk:merge - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:34780 7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:28489 b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:23202 + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:34798 7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:28489 b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:23202 Modified: trunk/refman-4.1/data-types.xml =================================================================== --- trunk/refman-4.1/data-types.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-4.1/data-types.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 556 bytes @@ -5473,7 +5473,7 @@ Normally, you search for SET values using the FIND_IN_SET() function or the - LIKE operator: + LIKE operator: Modified: trunk/refman-4.1/dba-core.xml =================================================================== --- trunk/refman-4.1/dba-core.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-4.1/dba-core.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 6, Lines Added: 7, Lines Deleted: 7; 2871 bytes @@ -6809,9 +6809,9 @@ - With a LIKE clause, the statement displays + With a LIKE clause, the statement displays only those variables that match the pattern. To obtain a - specific variable name, use a LIKE clause as + specific variable name, use a LIKE clause as shown: @@ -6823,7 +6823,7 @@ To get a list of variables whose name match a pattern, use the % wildcard character in a - LIKE clause: + LIKE clause: @@ -7098,7 +7098,7 @@ However, the following statement does not work. The variable is not interpreted as a compound name, but as a simple string - for a LIKE pattern-matching operation: + for a LIKE pattern-matching operation: @@ -13288,7 +13288,7 @@ _ in Host column values. These have the same meaning as for pattern-matching operations performed with - the LIKE operator. For example, a + the LIKE operator. For example, a Host value of '%' matches any hostname, whereas a value of '%.mysql.com' matches any host in the @@ -13815,7 +13815,7 @@ Host and Db columns of either table. These have the same meaning as for pattern-matching operations performed with the - LIKE operator. If you want to use either + LIKE operator. If you want to use either character literally when granting privileges, you must escape it with a backslash. For example, to include _ character as part of a @@ -13926,7 +13926,7 @@ and _ can be used in the Host column. These have the same meaning as for pattern-matching operations performed with the - LIKE operator. + LIKE operator. Modified: trunk/refman-4.1/errors-problems.xml =================================================================== --- trunk/refman-4.1/errors-problems.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-4.1/errors-problems.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 669 bytes @@ -5568,8 +5568,8 @@ You can't use _ or % with - ESCAPE in LIKE ... - ESCAPE. + ESCAPE in LIKE ... + ESCAPE. Modified: trunk/refman-4.1/functions-core.xml =================================================================== --- trunk/refman-4.1/functions-core.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-4.1/functions-core.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 12, Lines Added: 17, Lines Deleted: 17; 5187 bytes @@ -1628,7 +1628,7 @@ logical - XOR + XOR @@ -3622,8 +3622,8 @@ SOUNDS LIKE - expr1 SOUNDS LIKE - expr2 + expr1 SOUNDS LIKE + expr2 @@ -4092,9 +4092,9 @@ LIKE - expr LIKE + expr LIKE pat [ESCAPE - 'escape_char'] + 'escape_char'] @@ -4119,7 +4119,7 @@ - Per the SQL standard, LIKE performs + Per the SQL standard, LIKE performs matching on a per-character basis, thus it can produce results different from the = @@ -4142,7 +4142,7 @@ - With LIKE you can use the following two + With LIKE you can use the following two wildcard characters in the pattern: @@ -4235,9 +4235,9 @@ - In MySQL, LIKE is allowed on numeric + In MySQL, LIKE is allowed on numeric expressions. (This is an extension to the standard SQL - LIKE.) + LIKE.) @@ -4251,7 +4251,7 @@ example, \n to represent a newline character), you must double any \ that you use in - LIKE strings. For example, to search + LIKE strings. For example, to search for \n, specify it as \\n. To search for \, specify it as @@ -4277,9 +4277,9 @@ NOT LIKE - expr NOT LIKE + expr NOT LIKE pat [ESCAPE - 'escape_char'] + 'escape_char'] @@ -4297,7 +4297,7 @@ - Aggegate queries involving NOT LIKE + Aggegate queries involving NOT LIKE comparisons with columns containing NULL may yield unexpected results. For example, consider the following table and data: @@ -10519,10 +10519,10 @@ - MATCH + MATCH (col1,col2,...) AGAINST (expr - [search_modifier]) + [search_modifier]) @@ -12824,7 +12824,7 @@ CONVERT() function to convert the value to a non-binary string. If the character set of the result has a case-insensitive collation, the - LIKE operation is not case sensitive: + LIKE operation is not case sensitive: @@ -15980,7 +15980,7 @@ - Returns the bitwise XOR of all bits in + Returns the bitwise XOR of all bits in expr. The calculation is performed with 64-bit (BIGINT) precision. Modified: trunk/refman-4.1/internationalization.xml =================================================================== --- trunk/refman-4.1/internationalization.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-4.1/internationalization.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1041 bytes @@ -2511,7 +2511,7 @@ The SHOW CHARACTER SET command shows all available character sets. It takes an optional - LIKE clause that indicates which character + LIKE clause that indicates which character set names to match. For example: @@ -2530,7 +2530,7 @@ The output from SHOW COLLATION includes all available character sets. It takes an optional - LIKE clause that indicates which collation + LIKE clause that indicates which collation names to match. For example: Modified: trunk/refman-4.1/introduction.xml =================================================================== --- trunk/refman-4.1/introduction.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-4.1/introduction.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 522 bytes @@ -1820,7 +1820,7 @@ - LIKE is allowed on numeric values. + LIKE is allowed on numeric values. Modified: trunk/refman-4.1/language-structure.xml =================================================================== --- trunk/refman-4.1/language-structure.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-4.1/language-structure.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 826 bytes @@ -366,7 +366,7 @@ % and _ in pattern-matching contexts where they would otherwise be interpreted as wildcard - characters. See the description of the LIKE + characters. See the description of the LIKE operator in . If you use \% or \_ in non-pattern-matching Modified: trunk/refman-4.1/restrictions.xml =================================================================== --- trunk/refman-4.1/restrictions.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-4.1/restrictions.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 745 bytes @@ -776,7 +776,7 @@ The timers within MySQL used on Windows are of a lower precision than the timers used on Linux. For most situations you may not notice a difference, but the delay implied by a - call to SLEEP() on Windows and Linux may + call to SLEEP() on Windows and Linux may differ slightly due to the differences in precision. Modified: trunk/refman-4.1/sql-syntax.xml =================================================================== --- trunk/refman-4.1/sql-syntax.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-4.1/sql-syntax.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 6, Lines Added: 8, Lines Deleted: 8; 2713 bytes @@ -15276,8 +15276,8 @@ If the syntax for a given SHOW statement - includes a LIKE - 'pattern' part, + includes a LIKE + 'pattern' part, 'pattern' is a string that can contain the SQL % and @@ -15321,7 +15321,7 @@ The SHOW CHARACTER SET statement shows all available character sets. It takes an optional - LIKE clause that indicates which character + LIKE clause that indicates which character set names to match. For example: @@ -15376,7 +15376,7 @@ The output from SHOW COLLATION includes all available character sets. It takes an optional - LIKE clause whose + LIKE clause whose pattern indicates which collation names to match. For example: @@ -17010,7 +17010,7 @@ - With a LIKE clause, the statement displays + With a LIKE clause, the statement displays only rows for those variables with names that match the pattern: @@ -17507,10 +17507,10 @@ - With a LIKE clause, the statement displays + With a LIKE clause, the statement displays only rows for those variables with names that match the pattern. To obtain the row for a specific variable, use a - LIKE clause as shown: + LIKE clause as shown: @@ -17521,7 +17521,7 @@ To get a list of variables whose name match a pattern, use the % wildcard character in a - LIKE clause: + LIKE clause: Modified: trunk/refman-4.1/tutorial.xml =================================================================== --- trunk/refman-4.1/tutorial.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-4.1/tutorial.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 3, Lines Added: 4, Lines Deleted: 4; 1598 bytes @@ -2074,8 +2074,8 @@ MySQL, SQL patterns are case-insensitive by default. Some examples are shown here. Note that you do not use = or <> when you - use SQL patterns; use the LIKE or - NOT LIKE comparison operators instead. + use SQL patterns; use the LIKE or + NOT LIKE comparison operators instead. @@ -2195,7 +2195,7 @@ A REGEXP pattern match succeeds if the pattern matches anywhere in the value - being tested. (This differs from a LIKE + being tested. (This differs from a LIKE pattern match, which succeeds only if the pattern matches the entire value.) @@ -2215,7 +2215,7 @@ To demonstrate how extended regular expressions work, the - LIKE queries shown previously are rewritten + LIKE queries shown previously are rewritten here to use REGEXP. Modified: trunk/refman-5.0/data-types.xml =================================================================== --- trunk/refman-5.0/data-types.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.0/data-types.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 556 bytes @@ -5280,7 +5280,7 @@ Normally, you search for SET values using the FIND_IN_SET() function or the - LIKE operator: + LIKE operator: Modified: trunk/refman-5.0/dba-core.xml =================================================================== --- trunk/refman-5.0/dba-core.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.0/dba-core.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 6, Lines Added: 7, Lines Deleted: 7; 2875 bytes @@ -8083,9 +8083,9 @@ - With a LIKE clause, the statement displays + With a LIKE clause, the statement displays only those variables that match the pattern. To obtain a - specific variable name, use a LIKE clause as + specific variable name, use a LIKE clause as shown: @@ -8097,7 +8097,7 @@ To get a list of variables whose name match a pattern, use the % wildcard character in a - LIKE clause: + LIKE clause: @@ -8369,7 +8369,7 @@ However, the following statement does not work. The variable is not interpreted as a compound name, but as a simple string - for a LIKE pattern-matching operation: + for a LIKE pattern-matching operation: @@ -15415,7 +15415,7 @@ _ in Host column values. These have the same meaning as for pattern-matching operations performed with - the LIKE operator. For example, a + the LIKE operator. For example, a Host value of '%' matches any hostname, whereas a value of '%.mysql.com' matches any host in the @@ -15940,7 +15940,7 @@ Host and Db columns of either table. These have the same meaning as for pattern-matching operations performed with the - LIKE operator. If you want to use either + LIKE operator. If you want to use either character literally when granting privileges, you must escape it with a backslash. For example, to include the underscore character (_) @@ -16052,7 +16052,7 @@ and _ can be used in the Host column. These have the same meaning as for pattern-matching operations performed with the - LIKE operator. + LIKE operator. Modified: trunk/refman-5.0/errors-problems.xml =================================================================== --- trunk/refman-5.0/errors-problems.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.0/errors-problems.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 669 bytes @@ -5306,8 +5306,8 @@ You can't use _ or % with - ESCAPE in LIKE ... - ESCAPE. + ESCAPE in LIKE ... + ESCAPE. Modified: trunk/refman-5.0/faqs.xml =================================================================== --- trunk/refman-5.0/faqs.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.0/faqs.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 3, Lines Added: 5, Lines Deleted: 4; 1512 bytes @@ -6085,7 +6085,7 @@ - Why do some LIKE and + Why do some LIKE and FULLTEXT searches with CJK characters fail? @@ -6095,7 +6095,7 @@ - There is a very simple problem with LIKE + There is a very simple problem with LIKE searches on BINARY and BLOB columns: we need to know the end of a character. With multi-byte character sets, different @@ -6115,8 +6115,9 @@ If we don't know where the first character ends, then we don't know where the second character begins, in which case - even very simple searches such as LIKE - '_A%' fail. The solution is to use a regular CJK + even very simple searches such as LIKE + '_A%' fail. The solution is to use a regular CJK character set in the first place, or to convert to a CJK character set before comparing. Modified: trunk/refman-5.0/functions-core.xml =================================================================== --- trunk/refman-5.0/functions-core.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.0/functions-core.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 13, Lines Added: 18, Lines Deleted: 18; 5522 bytes @@ -1740,7 +1740,7 @@ logical - XOR + XOR @@ -3803,8 +3803,8 @@ SOUNDS LIKE - expr1 SOUNDS LIKE - expr2 + expr1 SOUNDS LIKE + expr2 @@ -4266,9 +4266,9 @@ LIKE - expr LIKE + expr LIKE pat [ESCAPE - 'escape_char'] + 'escape_char'] @@ -4293,7 +4293,7 @@ - Per the SQL standard, LIKE performs + Per the SQL standard, LIKE performs matching on a per-character basis, thus it can produce results different from the = @@ -4316,7 +4316,7 @@ - With LIKE you can use the following two + With LIKE you can use the following two wildcard characters in the pattern: @@ -4416,9 +4416,9 @@ - In MySQL, LIKE is allowed on numeric + In MySQL, LIKE is allowed on numeric expressions. (This is an extension to the standard SQL - LIKE.) + LIKE.) @@ -4432,7 +4432,7 @@ example, \n to represent a newline character), you must double any \ that you use in - LIKE strings. For example, to search + LIKE strings. For example, to search for \n, specify it as \\n. To search for \, specify it as @@ -4458,9 +4458,9 @@ NOT LIKE - expr NOT LIKE + expr NOT LIKE pat [ESCAPE - 'escape_char'] + 'escape_char'] @@ -4478,7 +4478,7 @@ - Aggregate queries involving NOT LIKE + Aggregate queries involving NOT LIKE comparisons with columns containing NULL may yield unexpected results. For example, consider the following table and data: @@ -10771,10 +10771,10 @@ - MATCH + MATCH (col1,col2,...) AGAINST (expr - [search_modifier]) + [search_modifier]) @@ -13030,7 +13030,7 @@ To perform a case-insensitive comparison, use the CONVERT() function to convert the value to a non-binary string. If the character set of the result - has a case-insensitive collation, the LIKE + has a case-insensitive collation, the LIKE operation is not case sensitive: @@ -15870,7 +15870,7 @@ SLEEP() - SLEEP(duration) + SLEEP(duration) @@ -16245,7 +16245,7 @@ - Returns the bitwise XOR of all bits in + Returns the bitwise XOR of all bits in expr. The calculation is performed with 64-bit (BIGINT) precision. Modified: trunk/refman-5.0/information-schema.xml =================================================================== --- trunk/refman-5.0/information-schema.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.0/information-schema.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 677 bytes @@ -3618,7 +3618,7 @@ SHOW statements that accept a - LIKE clause to limit the rows displayed have + LIKE clause to limit the rows displayed have been extended to allow a WHERE clause that enables specification of more general conditions that selected rows must satisfy: Modified: trunk/refman-5.0/internationalization.xml =================================================================== --- trunk/refman-5.0/internationalization.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.0/internationalization.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1041 bytes @@ -2694,7 +2694,7 @@ The SHOW CHARACTER SET command shows all available character sets. It takes an optional - LIKE clause that indicates which character + LIKE clause that indicates which character set names to match. For example: @@ -2713,7 +2713,7 @@ The output from SHOW COLLATION includes all available character sets. It takes an optional - LIKE clause that indicates which collation + LIKE clause that indicates which collation names to match. For example: Modified: trunk/refman-5.0/introduction.xml =================================================================== --- trunk/refman-5.0/introduction.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.0/introduction.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 522 bytes @@ -1496,7 +1496,7 @@ - LIKE is allowed on numeric values. + LIKE is allowed on numeric values. Modified: trunk/refman-5.0/language-structure-core.xml =================================================================== --- trunk/refman-5.0/language-structure-core.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.0/language-structure-core.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 841 bytes @@ -368,7 +368,7 @@ % and _ in pattern-matching contexts where they would otherwise be interpreted as wildcard - characters. See the description of the LIKE + characters. See the description of the LIKE operator in . If you use \% or \_ in non-pattern-matching Modified: trunk/refman-5.0/replication-configuration.xml =================================================================== --- trunk/refman-5.0/replication-configuration.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.0/replication-configuration.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 831 bytes @@ -2312,7 +2312,7 @@ and table name patterns. Patterns can contain the % and _ wildcard characters, which - have the same meaning as for the LIKE + have the same meaning as for the LIKE pattern-matching operator. To specify more than one table, use this option multiple times, once for each table. This works for cross-database updates. See Modified: trunk/refman-5.0/restrictions.xml =================================================================== --- trunk/refman-5.0/restrictions.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.0/restrictions.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 747 bytes @@ -1514,7 +1514,7 @@ The timers within MySQL used on Windows are of a lower precision than the timers used on Linux. For most situations you may not notice a difference, but the delay implied by a - call to SLEEP() on Windows and Linux may + call to SLEEP() on Windows and Linux may differ slightly due to the differences in precision. Modified: trunk/refman-5.0/sql-syntax.xml =================================================================== --- trunk/refman-5.0/sql-syntax.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.0/sql-syntax.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 18, Lines Added: 20, Lines Deleted: 20; 9075 bytes @@ -17287,8 +17287,8 @@ If the syntax for a given SHOW statement - includes a LIKE - 'pattern' part, + includes a LIKE + 'pattern' part, 'pattern' is a string that can contain the SQL % and @@ -17343,7 +17343,7 @@ The SHOW CHARACTER SET statement shows all - available character sets. The LIKE clause, + available character sets. The LIKE clause, if present, indicates which character set names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in @@ -17396,7 +17396,7 @@ The output from SHOW COLLATION includes all - available character sets. The LIKE clause, + available character sets. The LIKE clause, if present, indicates which collation names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in @@ -17468,7 +17468,7 @@ SHOW COLUMNS displays information about the columns in a given table. It also works for views as of MySQL - 5.0.1. The LIKE clause, if present, + 5.0.1. The LIKE clause, if present, indicates which column names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in @@ -17784,7 +17784,7 @@ SHOW DATABASES lists the databases on the MySQL server host. SHOW SCHEMAS is a synonym for SHOW DATABASES as of MySQL - 5.0.2. The LIKE clause, if present, + 5.0.2. The LIKE clause, if present, indicates which database names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in @@ -18586,7 +18586,7 @@ - The LIKE clause, if present, indicates + The LIKE clause, if present, indicates which event names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in . @@ -18887,7 +18887,7 @@ SHOW OPEN TABLES lists the non-TEMPORARY tables that are currently open in the table cache. See . - The LIKE clause, if present, indicates + The LIKE clause, if present, indicates which table names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in . @@ -18954,7 +18954,7 @@ - The FROM and LIKE + The FROM and LIKE clauses may be used as of MySQL 5.0.12. @@ -19148,7 +19148,7 @@ These statements are MySQL extensions. They return characteristics of routines, such as the database, name, type, creator, and creation and modification dates. The - LIKE clause, if present, indicates which + LIKE clause, if present, indicates which procedure or function names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in @@ -19788,7 +19788,7 @@ SHOW STATUS provides server status information. This information also can be obtained using the mysqladmin extended-status command. The - LIKE clause, if present, indicates which + LIKE clause, if present, indicates which variable names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in . @@ -19835,7 +19835,7 @@ - With a LIKE clause, the statement displays + With a LIKE clause, the statement displays only rows for those variables with names that match the pattern: @@ -19944,7 +19944,7 @@ TABLES, but provides a lot of information about each table. You can also get this list using the mysqlshow --status db_name command. - The LIKE clause, if present, indicates + The LIKE clause, if present, indicates which table names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in . @@ -20262,7 +20262,7 @@ non-TEMPORARY tables in a given database. You can also get this list using the mysqlshow db_name command. The - LIKE clause, if present, indicates which + LIKE clause, if present, indicates which table names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in . @@ -20327,7 +20327,7 @@ SHOW TRIGGERS lists the triggers currently defined on the MySQL server. This statement requires the SUPER privilege. It was implemented in - MySQL 5.0.10. The LIKE clause, if present, + MySQL 5.0.10. The LIKE clause, if present, indicates which trigger names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in @@ -20357,7 +20357,7 @@ - When using a LIKE clause with + When using a LIKE clause with SHOW TRIGGERS, the expression to be matched (expr) is compared with the name of the table on which the trigger is declared, and @@ -20524,7 +20524,7 @@ SHOW VARIABLES shows the values of MySQL system variables. This information also can be obtained using the mysqladmin variables command. The - LIKE clause, if present, indicates which + LIKE clause, if present, indicates which variable names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in . @@ -20607,10 +20607,10 @@ - With a LIKE clause, the statement displays + With a LIKE clause, the statement displays only rows for those variables with names that match the pattern. To obtain the row for a specific variable, use a - LIKE clause as shown: + LIKE clause as shown: @@ -20621,7 +20621,7 @@ To get a list of variables whose name match a pattern, use the % wildcard character in a - LIKE clause: + LIKE clause: Modified: trunk/refman-5.0/tutorial.xml =================================================================== --- trunk/refman-5.0/tutorial.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.0/tutorial.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 3, Lines Added: 4, Lines Deleted: 4; 1598 bytes @@ -2076,8 +2076,8 @@ MySQL, SQL patterns are case-insensitive by default. Some examples are shown here. Note that you do not use = or <> when you - use SQL patterns; use the LIKE or - NOT LIKE comparison operators instead. + use SQL patterns; use the LIKE or + NOT LIKE comparison operators instead. @@ -2197,7 +2197,7 @@ A REGEXP pattern match succeeds if the pattern matches anywhere in the value - being tested. (This differs from a LIKE + being tested. (This differs from a LIKE pattern match, which succeeds only if the pattern matches the entire value.) @@ -2217,7 +2217,7 @@ To demonstrate how extended regular expressions work, the - LIKE queries shown previously are rewritten + LIKE queries shown previously are rewritten here to use REGEXP. Modified: trunk/refman-5.1/ccsg-temp.xml =================================================================== --- trunk/refman-5.1/ccsg-temp.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.1/ccsg-temp.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 7, Lines Added: 10, Lines Deleted: 10; 4152 bytes @@ -22791,7 +22791,7 @@ - Other comparison operators such as LIKE + Other comparison operators such as LIKE and BETWEEN ... AND are likewise incompatible with the primary key lookup method. Each these operators specifies a range of values; none of them @@ -23286,7 +23286,7 @@ comparisons. The radically different organization of ordered indexes allows them be used with other comparison operators, such as less than, greater than and even - LIKE. For example, we used the + LIKE. For example, we used the following query to illustrate that it could not benefit at all from a the hash index: @@ -23342,7 +23342,7 @@ - LIKE, depending on the pattern that + LIKE, depending on the pattern that is matched @@ -23353,13 +23353,13 @@ The ... BETWEEN ... AND ... is completely equivalent to a ... >= ... AND ... <= ... expression. The - LIKE operator is a special case. + LIKE operator is a special case. - The LIKE operator tests to see if the + The LIKE operator tests to see if the value of the string expression appearing on the left hand - side of the LIKE keyword matches the + side of the LIKE keyword matches the pattern appearing on the right hand side. The pattern is also a string expression. The string value of the pattern is a collection of literal characters and optionally a @@ -23380,7 +23380,7 @@ A and is followed by zero or more arbitrary characters. So the % character denotes a wildcard that stands for zero or more - arbitrary characters. Any LIKE pattern + arbitrary characters. Any LIKE pattern whose string value does not start with a wildcard can be transformed into an range expression, and this is exactly what the MySQL Server will do. For example, the previous @@ -23396,9 +23396,9 @@ AND Name < 'B' - In this particular case of LIKE the + In this particular case of LIKE the ordered index can be used to perform a range scan. A - LIKE comparison can not be rewritten to + LIKE comparison can not be rewritten to a range expression if it starts with a wildcard. Consider the following query: @@ -23412,7 +23412,7 @@ Here the pattern starts with the % - wildcard, and the LIKE expression + wildcard, and the LIKE expression cannot be optimized to a range expression. However, this does not have to mean that ordered index is not used anymore. In this particular case, the values supplied for Modified: trunk/refman-5.1/data-types.xml =================================================================== --- trunk/refman-5.1/data-types.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.1/data-types.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 556 bytes @@ -4977,7 +4977,7 @@ Normally, you search for SET values using the FIND_IN_SET() function or the - LIKE operator: + LIKE operator: Modified: trunk/refman-5.1/dba-core-new-tmp.xml =================================================================== --- trunk/refman-5.1/dba-core-new-tmp.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.1/dba-core-new-tmp.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 6, Lines Added: 7, Lines Deleted: 7; 2899 bytes @@ -8622,9 +8622,9 @@ - With a LIKE clause, the statement displays + With a LIKE clause, the statement displays only those variables that match the pattern. To obtain a - specific variable name, use a LIKE clause as + specific variable name, use a LIKE clause as shown: @@ -8636,7 +8636,7 @@ To get a list of variables whose name match a pattern, use the % wildcard character in a - LIKE clause: + LIKE clause: @@ -8908,7 +8908,7 @@ However, the following statement does not work. The variable is not interpreted as a compound name, but as a simple string - for a LIKE pattern-matching operation: + for a LIKE pattern-matching operation: @@ -17297,7 +17297,7 @@ _ in Host column values. These have the same meaning as for pattern-matching operations performed with - the LIKE operator. For example, a + the LIKE operator. For example, a Host value of '%' matches any hostname, whereas a value of '%.mysql.com' matches any host in the @@ -17822,7 +17822,7 @@ Host and Db columns of either table. These have the same meaning as for pattern-matching operations performed with the - LIKE operator. If you want to use either + LIKE operator. If you want to use either character literally when granting privileges, you must escape it with a backslash. For example, to include the underscore character (_) @@ -17934,7 +17934,7 @@ and _ can be used in the Host column. These have the same meaning as for pattern-matching operations performed with the - LIKE operator. + LIKE operator. Modified: trunk/refman-5.1/dba-core.xml =================================================================== --- trunk/refman-5.1/dba-core.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.1/dba-core.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 6, Lines Added: 7, Lines Deleted: 7; 2875 bytes @@ -8609,9 +8609,9 @@ - With a LIKE clause, the statement displays + With a LIKE clause, the statement displays only those variables that match the pattern. To obtain a - specific variable name, use a LIKE clause as + specific variable name, use a LIKE clause as shown: @@ -8623,7 +8623,7 @@ To get a list of variables whose name match a pattern, use the % wildcard character in a - LIKE clause: + LIKE clause: @@ -8895,7 +8895,7 @@ However, the following statement does not work. The variable is not interpreted as a compound name, but as a simple string - for a LIKE pattern-matching operation: + for a LIKE pattern-matching operation: @@ -17363,7 +17363,7 @@ _ in Host column values. These have the same meaning as for pattern-matching operations performed with - the LIKE operator. For example, a + the LIKE operator. For example, a Host value of '%' matches any hostname, whereas a value of '%.mysql.com' matches any host in the @@ -17888,7 +17888,7 @@ Host and Db columns of either table. These have the same meaning as for pattern-matching operations performed with the - LIKE operator. If you want to use either + LIKE operator. If you want to use either character literally when granting privileges, you must escape it with a backslash. For example, to include the underscore character (_) @@ -18000,7 +18000,7 @@ and _ can be used in the Host column. These have the same meaning as for pattern-matching operations performed with the - LIKE operator. + LIKE operator. Modified: trunk/refman-5.1/errors-problems-core.xml =================================================================== --- trunk/refman-5.1/errors-problems-core.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.1/errors-problems-core.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 684 bytes @@ -5190,8 +5190,8 @@ You can't use _ or % with - ESCAPE in LIKE ... - ESCAPE. + ESCAPE in LIKE ... + ESCAPE. Modified: trunk/refman-5.1/faqs.xml =================================================================== --- trunk/refman-5.1/faqs.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.1/faqs.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 3, Lines Added: 5, Lines Deleted: 4; 1512 bytes @@ -6129,7 +6129,7 @@ - Why do some LIKE and + Why do some LIKE and FULLTEXT searches with CJK characters fail? @@ -6139,7 +6139,7 @@ - There is a very simple problem with LIKE + There is a very simple problem with LIKE searches on BINARY and BLOB columns: we need to know the end of a character. With multi-byte character sets, different @@ -6159,8 +6159,9 @@ If we don't know where the first character ends, then we don't know where the second character begins, in which case - even very simple searches such as LIKE - '_A%' fail. The solution is to use a regular CJK + even very simple searches such as LIKE + '_A%' fail. The solution is to use a regular CJK character set in the first place, or to convert to a CJK character set before comparing. Modified: trunk/refman-5.1/functions-core.xml =================================================================== --- trunk/refman-5.1/functions-core.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.1/functions-core.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 13, Lines Added: 18, Lines Deleted: 18; 5520 bytes @@ -1718,7 +1718,7 @@ logical - XOR + XOR @@ -3734,8 +3734,8 @@ SOUNDS LIKE - expr1 SOUNDS LIKE - expr2 + expr1 SOUNDS LIKE + expr2 @@ -4197,9 +4197,9 @@ LIKE - expr LIKE + expr LIKE pat [ESCAPE - 'escape_char'] + 'escape_char'] @@ -4224,7 +4224,7 @@ - Per the SQL standard, LIKE performs + Per the SQL standard, LIKE performs matching on a per-character basis, thus it can produce results different from the = @@ -4247,7 +4247,7 @@ - With LIKE you can use the following two + With LIKE you can use the following two wildcard characters in the pattern: @@ -4347,9 +4347,9 @@ - In MySQL, LIKE is allowed on numeric + In MySQL, LIKE is allowed on numeric expressions. (This is an extension to the standard SQL - LIKE.) + LIKE.) @@ -4363,7 +4363,7 @@ example, \n to represent a newline character), you must double any \ that you use in - LIKE strings. For example, to search + LIKE strings. For example, to search for \n, specify it as \\n. To search for \, specify it as @@ -4389,9 +4389,9 @@ NOT LIKE - expr NOT LIKE + expr NOT LIKE pat [ESCAPE - 'escape_char'] + 'escape_char'] @@ -4409,7 +4409,7 @@ - Aggegate queries involving NOT LIKE + Aggegate queries involving NOT LIKE comparisons with columns containing NULL may yield unexpected results. For example, consider the following table and data: @@ -10720,10 +10720,10 @@ - MATCH + MATCH (col1,col2,...) AGAINST (expr - [search_modifier]) + [search_modifier]) @@ -13002,7 +13002,7 @@ To perform a case-insensitive comparison, use the CONVERT() function to convert the value to a non-binary string. If the character set of the result - has a case-insensitive collation, the LIKE + has a case-insensitive collation, the LIKE operation is not case sensitive: @@ -16867,7 +16867,7 @@ SLEEP() - SLEEP(duration) + SLEEP(duration) @@ -17238,7 +17238,7 @@ - Returns the bitwise XOR of all bits in + Returns the bitwise XOR of all bits in expr. The calculation is performed with 64-bit (BIGINT) precision. Modified: trunk/refman-5.1/information-schema.xml =================================================================== --- trunk/refman-5.1/information-schema.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.1/information-schema.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 666 bytes @@ -5869,7 +5869,7 @@ SHOW statements that accept a - LIKE clause to limit the rows displayed also + LIKE clause to limit the rows displayed also allow a WHERE clause that enables specification of more general conditions that selected rows must satisfy: Modified: trunk/refman-5.1/internationalization.xml =================================================================== --- trunk/refman-5.1/internationalization.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.1/internationalization.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1041 bytes @@ -2692,7 +2692,7 @@ The SHOW CHARACTER SET command shows all available character sets. It takes an optional - LIKE clause that indicates which character + LIKE clause that indicates which character set names to match. For example: @@ -2711,7 +2711,7 @@ The output from SHOW COLLATION includes all available character sets. It takes an optional - LIKE clause that indicates which collation + LIKE clause that indicates which collation names to match. For example: Modified: trunk/refman-5.1/introduction.xml =================================================================== --- trunk/refman-5.1/introduction.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.1/introduction.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 522 bytes @@ -1707,7 +1707,7 @@ - LIKE is allowed on numeric values. + LIKE is allowed on numeric values. Modified: trunk/refman-5.1/language-structure-core.xml =================================================================== --- trunk/refman-5.1/language-structure-core.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.1/language-structure-core.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 841 bytes @@ -366,7 +366,7 @@ % and _ in pattern-matching contexts where they would otherwise be interpreted as wildcard - characters. See the description of the LIKE + characters. See the description of the LIKE operator in . If you use \% or \_ in non-pattern-matching Modified: trunk/refman-5.1/mysql-cluster-ccsg-merge-temp.xml =================================================================== --- trunk/refman-5.1/mysql-cluster-ccsg-merge-temp.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.1/mysql-cluster-ccsg-merge-temp.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 2, Lines Added: 3, Lines Deleted: 3; 1436 bytes @@ -14174,8 +14174,8 @@ In MySQL 5.1, this statement no longer supports a - LIKE clause. However, you can use - LIKE to filter queries against the + LIKE clause. However, you can use + LIKE to filter queries against the INFORMATION_SCHEMA.ENGINES, as discussed in the next item. @@ -14199,7 +14199,7 @@ INFORMATION_SCHEMA database (available beginning with MySQL 5.1.5). Unlike the case with the SHOW ENGINES statement, it is possible to - filter the results using a LIKE clause, + filter the results using a LIKE clause, and to select specific columns to obtain information that may be of use in scripts. For example, the following query shows whether the server was built with Modified: trunk/refman-5.1/mysql-cluster-management.xml =================================================================== --- trunk/refman-5.1/mysql-cluster-management.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.1/mysql-cluster-management.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 2, Lines Added: 3, Lines Deleted: 3; 1408 bytes @@ -2535,8 +2535,8 @@ In MySQL 5.1, this statement no longer supports a - LIKE clause. However, you can use - LIKE to filter queries against the + LIKE clause. However, you can use + LIKE to filter queries against the INFORMATION_SCHEMA.ENGINES, as discussed in the next item. @@ -2560,7 +2560,7 @@ INFORMATION_SCHEMA database (available beginning with MySQL 5.1.5). Unlike the case with the SHOW ENGINES statement, it is possible to - filter the results using a LIKE clause, and + filter the results using a LIKE clause, and to select specific columns to obtain information that may be of use in scripts. For example, the following query shows whether the server was built with NDB Modified: trunk/refman-5.1/partitioning-guide.xml =================================================================== --- trunk/refman-5.1/partitioning-guide.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.1/partitioning-guide.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 841 bytes @@ -4032,7 +4032,7 @@ output of SHOW TABLE STATUS, with the addition of columns showing the data and index directories used for the partition. This command is likely to support - LIKE and FROM clauses + LIKE and FROM clauses that will make it possible to obtain information about a given partition by name, or about partitions belonging to specific table or database. Modified: trunk/refman-5.1/replication-configuration.xml =================================================================== --- trunk/refman-5.1/replication-configuration.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.1/replication-configuration.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 831 bytes @@ -2867,7 +2867,7 @@ and table name patterns. Patterns can contain the % and _ wildcard characters, which - have the same meaning as for the LIKE + have the same meaning as for the LIKE pattern-matching operator. To specify more than one table, use this option multiple times, once for each table. This works for cross-database updates. See Modified: trunk/refman-5.1/restrictions.xml =================================================================== --- trunk/refman-5.1/restrictions.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.1/restrictions.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 747 bytes @@ -1553,7 +1553,7 @@ The timers within MySQL used on Windows are of a lower precision than the timers used on Linux. For most situations you may not notice a difference, but the delay implied by a - call to SLEEP() on Windows and Linux may + call to SLEEP() on Windows and Linux may differ slightly due to the differences in precision. Modified: trunk/refman-5.1/sql-syntax.xml =================================================================== --- trunk/refman-5.1/sql-syntax.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.1/sql-syntax.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 18, Lines Added: 20, Lines Deleted: 20; 9135 bytes @@ -19666,8 +19666,8 @@ If the syntax for a given SHOW statement - includes a LIKE - 'pattern' part, + includes a LIKE + 'pattern' part, 'pattern' is a string that can contain the SQL % and @@ -19760,7 +19760,7 @@ The SHOW CHARACTER SET statement shows all - available character sets. The LIKE clause, + available character sets. The LIKE clause, if present, indicates which character set names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in @@ -19813,7 +19813,7 @@ The output from SHOW COLLATION includes all - available character sets. The LIKE clause, + available character sets. The LIKE clause, if present, indicates which collation names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in @@ -19885,7 +19885,7 @@ SHOW COLUMNS displays information about the columns in a given table. It also works for views. The - LIKE clause, if present, indicates which + LIKE clause, if present, indicates which column names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in . @@ -20377,7 +20377,7 @@ SHOW DATABASES lists the databases on the MySQL server host. SHOW SCHEMAS is a synonym for SHOW DATABASES. The - LIKE clause, if present, indicates which + LIKE clause, if present, indicates which database names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in . @@ -21195,7 +21195,7 @@ - The LIKE clause, if present, indicates + The LIKE clause, if present, indicates which event names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in . @@ -21402,7 +21402,7 @@ You can filter the list returned by this statement on the - event name using LIKE plus a pattern. + event name using LIKE plus a pattern. @@ -21802,7 +21802,7 @@ SHOW OPEN TABLES lists the non-TEMPORARY tables that are currently open in the table cache. See . - The LIKE clause, if present, indicates + The LIKE clause, if present, indicates which table names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in . @@ -22112,7 +22112,7 @@ These statements are MySQL extensions. They return characteristics of routines, such as the database, name, type, creator, creation and modification dates, and character set - information. The LIKE clause, if present, + information. The LIKE clause, if present, indicates which procedure or function names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in @@ -22534,7 +22534,7 @@ SHOW STATUS provides server status information. This information also can be obtained using the mysqladmin extended-status command. The - LIKE clause, if present, indicates which + LIKE clause, if present, indicates which variable names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in . @@ -22581,7 +22581,7 @@ - With a LIKE clause, the statement displays + With a LIKE clause, the statement displays only rows for those variables with names that match the pattern: @@ -22673,7 +22673,7 @@ TABLES, but provides a lot of information about each table. You can also get this list using the mysqlshow --status db_name command. - The LIKE clause, if present, indicates + The LIKE clause, if present, indicates which table names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in . @@ -22987,7 +22987,7 @@ non-TEMPORARY tables in a given database. You can also get this list using the mysqlshow db_name command. The - LIKE clause, if present, indicates which + LIKE clause, if present, indicates which table names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in . @@ -23050,7 +23050,7 @@ defined on the MySQL server. This statement requires the TRIGGER privilege (prior to MySQL 5.1.22, it requires the SUPER privilege). The - LIKE clause, if present, indicates which + LIKE clause, if present, indicates which trigger names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in . @@ -23094,7 +23094,7 @@ - When using a LIKE clause with + When using a LIKE clause with SHOW TRIGGERS, the expression to be matched (expr) is compared with the name of the table on which the trigger is declared, and @@ -23254,7 +23254,7 @@ SHOW VARIABLES shows the values of MySQL system variables. This information also can be obtained using the mysqladmin variables command. The - LIKE clause, if present, indicates which + LIKE clause, if present, indicates which variable names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in . @@ -23345,10 +23345,10 @@ - With a LIKE clause, the statement displays + With a LIKE clause, the statement displays only rows for those variables with names that match the pattern. To obtain the row for a specific variable, use a - LIKE clause as shown: + LIKE clause as shown: @@ -23359,7 +23359,7 @@ To get a list of variables whose name match a pattern, use the % wildcard character in a - LIKE clause: + LIKE clause: Modified: trunk/refman-5.1/tutorial.xml =================================================================== --- trunk/refman-5.1/tutorial.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-5.1/tutorial.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 3, Lines Added: 4, Lines Deleted: 4; 1598 bytes @@ -2065,8 +2065,8 @@ MySQL, SQL patterns are case-insensitive by default. Some examples are shown here. Note that you do not use = or <> when you - use SQL patterns; use the LIKE or - NOT LIKE comparison operators instead. + use SQL patterns; use the LIKE or + NOT LIKE comparison operators instead. @@ -2186,7 +2186,7 @@ A REGEXP pattern match succeeds if the pattern matches anywhere in the value - being tested. (This differs from a LIKE + being tested. (This differs from a LIKE pattern match, which succeeds only if the pattern matches the entire value.) @@ -2206,7 +2206,7 @@ To demonstrate how extended regular expressions work, the - LIKE queries shown previously are rewritten + LIKE queries shown previously are rewritten here to use REGEXP. Modified: trunk/refman-6.0/data-types.xml =================================================================== --- trunk/refman-6.0/data-types.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-6.0/data-types.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 556 bytes @@ -4970,7 +4970,7 @@ Normally, you search for SET values using the FIND_IN_SET() function or the - LIKE operator: + LIKE operator: Modified: trunk/refman-6.0/dba-core.xml =================================================================== --- trunk/refman-6.0/dba-core.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-6.0/dba-core.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 6, Lines Added: 7, Lines Deleted: 7; 2875 bytes @@ -8307,9 +8307,9 @@ - With a LIKE clause, the statement displays + With a LIKE clause, the statement displays only those variables that match the pattern. To obtain a - specific variable name, use a LIKE clause as + specific variable name, use a LIKE clause as shown: @@ -8321,7 +8321,7 @@ To get a list of variables whose name match a pattern, use the % wildcard character in a - LIKE clause: + LIKE clause: @@ -8593,7 +8593,7 @@ However, the following statement does not work. The variable is not interpreted as a compound name, but as a simple string - for a LIKE pattern-matching operation: + for a LIKE pattern-matching operation: @@ -16894,7 +16894,7 @@ _ in Host column values. These have the same meaning as for pattern-matching operations performed with - the LIKE operator. For example, a + the LIKE operator. For example, a Host value of '%' matches any hostname, whereas a value of '%.mysql.com' matches any host in the @@ -17419,7 +17419,7 @@ Host and Db columns of either table. These have the same meaning as for pattern-matching operations performed with the - LIKE operator. If you want to use either + LIKE operator. If you want to use either character literally when granting privileges, you must escape it with a backslash. For example, to include the underscore character (_) @@ -17531,7 +17531,7 @@ and _ can be used in the Host column. These have the same meaning as for pattern-matching operations performed with the - LIKE operator. + LIKE operator. Modified: trunk/refman-6.0/errors-problems.xml =================================================================== --- trunk/refman-6.0/errors-problems.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-6.0/errors-problems.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 669 bytes @@ -5185,8 +5185,8 @@ You can't use _ or % with - ESCAPE in LIKE ... - ESCAPE. + ESCAPE in LIKE ... + ESCAPE. Modified: trunk/refman-6.0/faqs.xml =================================================================== --- trunk/refman-6.0/faqs.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-6.0/faqs.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 3, Lines Added: 5, Lines Deleted: 4; 1512 bytes @@ -6131,7 +6131,7 @@ - Why do some LIKE and + Why do some LIKE and FULLTEXT searches with CJK characters fail? @@ -6141,7 +6141,7 @@ - There is a very simple problem with LIKE + There is a very simple problem with LIKE searches on BINARY and BLOB columns: we need to know the end of a character. With multi-byte character sets, different @@ -6161,8 +6161,9 @@ If we don't know where the first character ends, then we don't know where the second character begins, in which case - even very simple searches such as LIKE - '_A%' fail. The solution is to use a regular CJK + even very simple searches such as LIKE + '_A%' fail. The solution is to use a regular CJK character set in the first place, or to convert to a CJK character set before comparing. Modified: trunk/refman-6.0/functions-core.xml =================================================================== --- trunk/refman-6.0/functions-core.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-6.0/functions-core.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 13, Lines Added: 18, Lines Deleted: 18; 5520 bytes @@ -1718,7 +1718,7 @@ logical - XOR + XOR @@ -3733,8 +3733,8 @@ SOUNDS LIKE - expr1 SOUNDS LIKE - expr2 + expr1 SOUNDS LIKE + expr2 @@ -4534,9 +4534,9 @@ LIKE - expr LIKE + expr LIKE pat [ESCAPE - 'escape_char'] + 'escape_char'] @@ -4561,7 +4561,7 @@ - Per the SQL standard, LIKE performs + Per the SQL standard, LIKE performs matching on a per-character basis, thus it can produce results different from the = @@ -4584,7 +4584,7 @@ - With LIKE you can use the following two + With LIKE you can use the following two wildcard characters in the pattern: @@ -4683,9 +4683,9 @@ - In MySQL, LIKE is allowed on numeric + In MySQL, LIKE is allowed on numeric expressions. (This is an extension to the standard SQL - LIKE.) + LIKE.) @@ -4699,7 +4699,7 @@ example, \n to represent a newline character), you must double any \ that you use in - LIKE strings. For example, to search + LIKE strings. For example, to search for \n, specify it as \\n. To search for \, specify it as @@ -4725,9 +4725,9 @@ NOT LIKE - expr NOT LIKE + expr NOT LIKE pat [ESCAPE - 'escape_char'] + 'escape_char'] @@ -4745,7 +4745,7 @@ - Aggegate queries involving NOT LIKE + Aggegate queries involving NOT LIKE comparisons with columns containing NULL may yield unexpected results. For example, consider the following table and data: @@ -11043,10 +11043,10 @@ - MATCH + MATCH (col1,col2,...) AGAINST (expr - [search_modifier]) + [search_modifier]) @@ -13326,7 +13326,7 @@ To perform a case-insensitive comparison, use the CONVERT() function to convert the value to a non-binary string. If the character set of the result - has a case-insensitive collation, the LIKE + has a case-insensitive collation, the LIKE operation is not case sensitive: @@ -17169,7 +17169,7 @@ SLEEP() - SLEEP(duration) + SLEEP(duration) @@ -17540,7 +17540,7 @@ - Returns the bitwise XOR of all bits in + Returns the bitwise XOR of all bits in expr. The calculation is performed with 64-bit (BIGINT) precision. Modified: trunk/refman-6.0/information-schema.xml =================================================================== --- trunk/refman-6.0/information-schema.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-6.0/information-schema.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 666 bytes @@ -6017,7 +6017,7 @@ SHOW statements that accept a - LIKE clause to limit the rows displayed also + LIKE clause to limit the rows displayed also allow a WHERE clause that enables specification of more general conditions that selected rows must satisfy: Modified: trunk/refman-6.0/internationalization.xml =================================================================== --- trunk/refman-6.0/internationalization.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-6.0/internationalization.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1041 bytes @@ -2693,7 +2693,7 @@ The SHOW CHARACTER SET command shows all available character sets. It takes an optional - LIKE clause that indicates which character + LIKE clause that indicates which character set names to match. For example: @@ -2712,7 +2712,7 @@ The output from SHOW COLLATION includes all available character sets. It takes an optional - LIKE clause that indicates which collation + LIKE clause that indicates which collation names to match. For example: Modified: trunk/refman-6.0/introduction.xml =================================================================== --- trunk/refman-6.0/introduction.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-6.0/introduction.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 522 bytes @@ -1461,7 +1461,7 @@ - LIKE is allowed on numeric values. + LIKE is allowed on numeric values. Modified: trunk/refman-6.0/language-structure-core.xml =================================================================== --- trunk/refman-6.0/language-structure-core.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-6.0/language-structure-core.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 841 bytes @@ -366,7 +366,7 @@ % and _ in pattern-matching contexts where they would otherwise be interpreted as wildcard - characters. See the description of the LIKE + characters. See the description of the LIKE operator in . If you use \% or \_ in non-pattern-matching Modified: trunk/refman-6.0/mysql-cluster-management.xml =================================================================== --- trunk/refman-6.0/mysql-cluster-management.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-6.0/mysql-cluster-management.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 881 bytes @@ -2530,7 +2530,7 @@ INFORMATION_SCHEMA database (available beginning with MySQL 5.1.5). Unlike the case with the SHOW ENGINES statement, it is possible to - filter the results using a LIKE clause, and + filter the results using a LIKE clause, and to select specific columns to obtain information that may be of use in scripts. For example, the following query shows whether the server was built with NDB Modified: trunk/refman-6.0/partitioning-guide.xml =================================================================== --- trunk/refman-6.0/partitioning-guide.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-6.0/partitioning-guide.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 841 bytes @@ -3955,7 +3955,7 @@ output of SHOW TABLE STATUS, with the addition of columns showing the data and index directories used for the partition. This command is likely to support - LIKE and FROM clauses + LIKE and FROM clauses that will make it possible to obtain information about a given partition by name, or about partitions belonging to specific table or database. Modified: trunk/refman-6.0/replication-configuration.xml =================================================================== --- trunk/refman-6.0/replication-configuration.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-6.0/replication-configuration.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 831 bytes @@ -2840,7 +2840,7 @@ and table name patterns. Patterns can contain the % and _ wildcard characters, which - have the same meaning as for the LIKE + have the same meaning as for the LIKE pattern-matching operator. To specify more than one table, use this option multiple times, once for each table. This works for cross-database updates. See Modified: trunk/refman-6.0/restrictions.xml =================================================================== --- trunk/refman-6.0/restrictions.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-6.0/restrictions.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 747 bytes @@ -1524,7 +1524,7 @@ The timers within MySQL used on Windows are of a lower precision than the timers used on Linux. For most situations you may not notice a difference, but the delay implied by a - call to SLEEP() on Windows and Linux may + call to SLEEP() on Windows and Linux may differ slightly due to the differences in precision. Modified: trunk/refman-6.0/sql-syntax.xml =================================================================== --- trunk/refman-6.0/sql-syntax.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-6.0/sql-syntax.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 18, Lines Added: 20, Lines Deleted: 20; 9121 bytes @@ -20087,8 +20087,8 @@ If the syntax for a given SHOW statement - includes a LIKE - 'pattern' part, + includes a LIKE + 'pattern' part, 'pattern' is a string that can contain the SQL % and @@ -20177,7 +20177,7 @@ The SHOW CHARACTER SET statement shows all - available character sets. The LIKE clause, + available character sets. The LIKE clause, if present, indicates which character set names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in @@ -20230,7 +20230,7 @@ The output from SHOW COLLATION includes all - available character sets. The LIKE clause, + available character sets. The LIKE clause, if present, indicates which collation names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in @@ -20302,7 +20302,7 @@ SHOW COLUMNS displays information about the columns in a given table. It also works for views. The - LIKE clause, if present, indicates which + LIKE clause, if present, indicates which column names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in . @@ -20779,7 +20779,7 @@ SHOW DATABASES lists the databases on the MySQL server host. SHOW SCHEMAS is a synonym for SHOW DATABASES. The - LIKE clause, if present, indicates which + LIKE clause, if present, indicates which database names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in . @@ -21523,7 +21523,7 @@ - The LIKE clause, if present, indicates + The LIKE clause, if present, indicates which event names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in . @@ -21714,7 +21714,7 @@ You can filter the list returned by this statement on the - event name using LIKE plus a pattern. + event name using LIKE plus a pattern. @@ -22110,7 +22110,7 @@ SHOW OPEN TABLES lists the non-TEMPORARY tables that are currently open in the table cache. See . - The LIKE clause, if present, indicates + The LIKE clause, if present, indicates which table names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in . @@ -22409,7 +22409,7 @@ These statements are MySQL extensions. They return characteristics of routines, such as the database, name, type, creator, creation and modification dates, and character set - information. The LIKE clause, if present, + information. The LIKE clause, if present, indicates which procedure or function names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in @@ -22768,7 +22768,7 @@ SHOW STATUS provides server status information. This information also can be obtained using the mysqladmin extended-status command. The - LIKE clause, if present, indicates which + LIKE clause, if present, indicates which variable names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in . @@ -22815,7 +22815,7 @@ - With a LIKE clause, the statement displays + With a LIKE clause, the statement displays only rows for those variables with names that match the pattern: @@ -22907,7 +22907,7 @@ TABLES, but provides a lot of information about each table. You can also get this list using the mysqlshow --status db_name command. - The LIKE clause, if present, indicates + The LIKE clause, if present, indicates which table names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in . @@ -23221,7 +23221,7 @@ non-TEMPORARY tables in a given database. You can also get this list using the mysqlshow db_name command. The - LIKE clause, if present, indicates which + LIKE clause, if present, indicates which table names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in . @@ -23283,7 +23283,7 @@ SHOW TRIGGERS lists the triggers currently defined on the MySQL server. This statement requires the TRIGGER privilege. The - LIKE clause, if present, indicates which + LIKE clause, if present, indicates which trigger names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in . @@ -23326,7 +23326,7 @@ - When using a LIKE clause with + When using a LIKE clause with SHOW TRIGGERS, the expression to be matched (expr) is compared with the name of the table on which the trigger is declared, and @@ -23486,7 +23486,7 @@ SHOW VARIABLES shows the values of MySQL system variables. This information also can be obtained using the mysqladmin variables command. The - LIKE clause, if present, indicates which + LIKE clause, if present, indicates which variable names to match. The WHERE clause can be given to select rows using more general conditions, as discussed in . @@ -23586,10 +23586,10 @@ - With a LIKE clause, the statement displays + With a LIKE clause, the statement displays only rows for those variables with names that match the pattern. To obtain the row for a specific variable, use a - LIKE clause as shown: + LIKE clause as shown: @@ -23600,7 +23600,7 @@ To get a list of variables whose name match a pattern, use the % wildcard character in a - LIKE clause: + LIKE clause: Modified: trunk/refman-6.0/tutorial.xml =================================================================== --- trunk/refman-6.0/tutorial.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-6.0/tutorial.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 3, Lines Added: 4, Lines Deleted: 4; 1598 bytes @@ -2065,8 +2065,8 @@ MySQL, SQL patterns are case-insensitive by default. Some examples are shown here. Note that you do not use = or <> when you - use SQL patterns; use the LIKE or - NOT LIKE comparison operators instead. + use SQL patterns; use the LIKE or + NOT LIKE comparison operators instead. @@ -2186,7 +2186,7 @@ A REGEXP pattern match succeeds if the pattern matches anywhere in the value - being tested. (This differs from a LIKE + being tested. (This differs from a LIKE pattern match, which succeeds only if the pattern matches the entire value.) @@ -2206,7 +2206,7 @@ To demonstrate how extended regular expressions work, the - LIKE queries shown previously are rewritten + LIKE queries shown previously are rewritten here to use REGEXP. Modified: trunk/refman-common/news-innodb.xml =================================================================== --- trunk/refman-common/news-innodb.xml 2008-01-09 17:14:19 UTC (rev 9534) +++ trunk/refman-common/news-innodb.xml 2008-01-09 19:14:38 UTC (rev 9535) Changed blocks: 1, Lines Added: 2, Lines Deleted: 1; 677 bytes @@ -500,7 +500,8 @@ - Fixed a bug: in LIKE 'abc%', the + Fixed a bug: in LIKE +'abc%', the '%' did not match the empty string if the character set was not latin1_swedish_ci. This bug was fixed by changing the sorting order in these