Below is the list of changes that have just been committed into a local
mysqldoc repository of root. When root does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://www.mysql.com/doc/I/n/Installing_source_tree.html
ChangeSet
1.3225 05/08/11 12:25:34 Mike.Hillyer@stripped +2 -0
Feature request edits.
refman/functions.xml
1.23 05/08/11 12:25:33 Mike.Hillyer@stripped +17 -13
Quick edits to close a couple of feature requests.
refman-5.1/functions.xml
1.3 05/08/11 12:25:33 Mike.Hillyer@stripped +12 -8
sync
# This is a BitKeeper patch. What follows are the unified diffs for the
# set of deltas contained in the patch. The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User: Mike.Hillyer
# Host: www.openwin.org
# Root: /home/mysqldoc/mysqldoc
--- 1.2/refman-5.1/functions.xml 2005-08-08 20:53:04 -06:00
+++ 1.3/refman-5.1/functions.xml 2005-08-11 12:25:33 -06:00
@@ -7275,7 +7275,7 @@
<para>
Extracts the time part of the time or datetime expression
- <replaceable>expr</replaceable>.
+ <replaceable>expr</replaceable> and returns it as a string.
</para>
<!-- end_description_for_help_topic -->
@@ -8387,8 +8387,8 @@
such as <quote>the</quote> or <quote>some</quote> that is so
common that it is considered to have zero semantic value.
There is a built-in stopword list, but it can be overwritten
- by a user-defined list.
- See <xref linkend="fulltext-fine-tuning"/>.
+ by a user-defined list. See
+ <xref linkend="fulltext-fine-tuning"/>.
</para>
</listitem>
@@ -8453,7 +8453,9 @@
insert only one or two rows of text into it, every word in the
text occurs in at least 50% of the rows. As a result, no search
returns any results. Be sure to insert at least three rows, and
- preferably many more.
+ preferably many more. Users who need to bypass the 50% limitation
+ can use the boolean search mode, see
+ <xref linkend="fulltext-boolean" />.
</para>
<section id="fulltext-boolean">
@@ -8973,10 +8975,12 @@
<primary>stopword list</primary>
<secondary>user-defined</secondary>
</indexterm>
+
<indexterm type="function">
<primary>fulltext</primary>
<secondary>stopword list</secondary>
</indexterm>
+
To override the default stopword list, set the
<literal>ft_stopword_file</literal> system variable. (See
<xref linkend="server-system-variables"/>.) The variable
@@ -8986,15 +8990,15 @@
contents of the stopword file, rebuild your
<literal>FULLTEXT</literal> indexes.
</para>
+
<para>
The stopword list is free-form, that is, you may use any
- non-alphanumeric character such as newline, space, or comma
- to separate stopwords. Exceptions are the underscore
+ non-alphanumeric character such as newline, space, or comma
+ to separate stopwords. Exceptions are the underscore
character (<literal>_</literal>) and a single apostrophe
(<literal>'</literal>) which are treated as part of a word.
The character set of the stopword list is the server's
- default character set;
- see <xref linkend="charset-server"/>.
+ default character set; see <xref linkend="charset-server"/>.
</para>
</listitem>
--- 1.22/refman/functions.xml 2005-08-08 20:53:12 -06:00
+++ 1.23/refman/functions.xml 2005-08-11 12:25:33 -06:00
@@ -281,8 +281,8 @@
<para>
By default, string comparisons are not case sensitive and use
- the current character set (cp1252 Latin1 by default, which
- also works excellently for English).
+ the current character set (cp1252 Latin1 by default, which also
+ works excellently for English).
</para>
<para>
@@ -3870,9 +3870,9 @@
<para>
<literal>REGEXP</literal> and <literal>RLIKE</literal> use
- the current character set (cp1252 Latin1 by default)
- when deciding the type of a character. However, these
- operators are not multi-byte safe.
+ the current character set (cp1252 Latin1 by default) when
+ deciding the type of a character. However, these operators
+ are not multi-byte safe.
</para>
<!-- description_for_help_topic STRCMP -->
@@ -7388,7 +7388,7 @@
<para>
Extracts the time part of the time or datetime expression
- <replaceable>expr</replaceable>.
+ <replaceable>expr</replaceable> and returns it as a string.
</para>
<!-- end_description_for_help_topic -->
@@ -8549,8 +8549,8 @@
such as <quote>the</quote> or <quote>some</quote> that is so
common that it is considered to have zero semantic value.
There is a built-in stopword list, but it can be overwritten
- by a user-defined list.
- See <xref linkend="fulltext-fine-tuning"/>.
+ by a user-defined list. See
+ <xref linkend="fulltext-fine-tuning"/>.
</para>
</listitem>
@@ -8615,7 +8615,9 @@
insert only one or two rows of text into it, every word in the
text occurs in at least 50% of the rows. As a result, no search
returns any results. Be sure to insert at least three rows, and
- preferably many more.
+ preferably many more. Users who need to bypass the 50% limitation
+ can use the boolean search mode, see
+ <xref linkend="fulltext-boolean" />.
</para>
<section id="fulltext-boolean">
@@ -9138,10 +9140,12 @@
<primary>stopword list</primary>
<secondary>user-defined</secondary>
</indexterm>
+
<indexterm type="function">
<primary>fulltext</primary>
<secondary>stopword list</secondary>
</indexterm>
+
To override the default stopword list, set the
<literal>ft_stopword_file</literal> system variable
(available as of MySQL 4.0.10). See
@@ -9152,15 +9156,15 @@
contents of the stopword file, rebuild your
<literal>FULLTEXT</literal> indexes.
</para>
+
<para>
The stopword list is free-form, that is, you may use any
- non-alphanumeric character such as newline, space, or comma
- to separate stopwords. Exceptions are the underscore
+ non-alphanumeric character such as newline, space, or comma
+ to separate stopwords. Exceptions are the underscore
character (<literal>_</literal>) and a single apostrophe
(<literal>'</literal>) which are treated as part of a word.
The character set of the stopword list is the server's
- default character set;
- see <xref linkend="charset-server"/>.
+ default character set; see <xref linkend="charset-server"/>.
</para>
</listitem>
| Thread |
|---|
| • bk commit - mysqldoc@docsrva tree (Mike.Hillyer:1.3225) | mhillyer | 11 Aug |
