Author: paul
Date: 2005-12-13 19:10:55 +0100 (Tue, 13 Dec 2005)
New Revision: 553
Log:
r4743@frost: paul | 2005-12-13 09:26:34 -0600
Mention new WITH PARSER clause for FULLTEXT index creation.
Modified:
trunk/
trunk/refman-5.1/installing.xml
trunk/refman-5.1/sql-syntax.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:4742
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1609
+ b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:4743
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1609
Modified: trunk/refman-5.1/installing.xml
===================================================================
--- trunk/refman-5.1/installing.xml 2005-12-13 18:10:37 UTC (rev 552)
+++ trunk/refman-5.1/installing.xml 2005-12-13 18:10:55 UTC (rev 553)
@@ -12211,6 +12211,17 @@
</para>
</listitem>
+ <listitem>
+ <para>
+ The <literal>INSTALL PLUGIN</literal> and <literal>UNINSTALL
+ PLUGIN</literal> statements that are used for the plugin API
+ are new. So is the <literal>WITH PARSER</literal> clause for
+ <literal>FULLTEXT</literal> index creation that associates a
+ parser plugin with a full-text index.
+ <xref linkend="plugin-api"/>.
+ </para>
+ </listitem>
+
</itemizedlist>
<remark>
Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml 2005-12-13 18:10:37 UTC (rev 552)
+++ trunk/refman-5.1/sql-syntax.xml 2005-12-13 18:10:55 UTC (rev 553)
@@ -123,7 +123,7 @@
ADD ALTER AFTER AVG_ROW_LENGTH BY COLUMN FIRST INDEX PRIMARY KEY
KEYS UNIQUE FULLTEXT SPATIAL CONSTRAINT DROP DISABLE ENABLE
RENAME ORDER MODIFY CHANGE DEFAULT SET FOREIGN IGNORE ENGINE
- TYPE
+ TYPE WITH PARSER
</remark>
<remark role="help-syntax"/>
@@ -139,8 +139,10 @@
| ADD [CONSTRAINT [<replaceable>symbol</replaceable>]]
PRIMARY KEY [<replaceable>index_type</replaceable>] (<replaceable>index_col_name</replaceable>,...)
| ADD [CONSTRAINT [<replaceable>symbol</replaceable>]]
- UNIQUE [<replaceable>index_name</replaceable>] [<replaceable>index_type</replaceable>] (<replaceable>index_col_name</replaceable>,...)
- | ADD [FULLTEXT|SPATIAL] [<replaceable>index_name</replaceable>] (<replaceable>index_col_name</replaceable>,...)
+ UNIQUE [INDEX] [<replaceable>index_name</replaceable>] [<replaceable>index_type</replaceable>] (<replaceable>index_col_name</replaceable>,...)
+ | ADD FULLTEXT [INDEX] [<replaceable>index_name</replaceable>] (<replaceable>index_col_name</replaceable>,...)
+ [WITH PARSER <replaceable>parser_name</replaceable>]
+ | ADD SPATIAL [INDEX] [<replaceable>index_name</replaceable>] (<replaceable>index_col_name</replaceable>,...)
| ADD [CONSTRAINT [<replaceable>symbol</replaceable>]]
FOREIGN KEY [<replaceable>index_name</replaceable>] (<replaceable>index_col_name</replaceable>,...)
[<replaceable>reference_definition</replaceable>]
@@ -1225,7 +1227,7 @@
<remark role="help-topic" condition="CREATE INDEX"/>
<remark role="help-keywords">
- BTREE RTREE INDEX CREATE FULLTEXT SPATIAL
+ BTREE RTREE INDEX CREATE FULLTEXT SPATIAL WITH PARSER
</remark>
<remark role="help-syntax"/>
@@ -1234,6 +1236,7 @@
CREATE [UNIQUE|FULLTEXT|SPATIAL] INDEX <replaceable>index_name</replaceable>
[USING <replaceable>index_type</replaceable>]
ON <replaceable>tbl_name</replaceable> (<replaceable>index_col_name</replaceable>,...)
+ [WITH PARSER <replaceable>parser_name</replaceable>]
<replaceable>index_col_name</replaceable>:
<replaceable>col_name</replaceable> [(<replaceable>length</replaceable>)] [ASC | DESC]
@@ -1407,15 +1410,20 @@
</para>
<para>
- <literal>FULLTEXT</literal> indexes can index only
+ <literal>FULLTEXT</literal> indexes can include only
<literal>CHAR</literal>, <literal>VARCHAR</literal>, and
<literal>TEXT</literal> columns, and only in
<literal>MyISAM</literal> tables. See
- <xref linkend="fulltext-search"/>.
+ <xref linkend="fulltext-search"/>. A <literal>WITH
+ PARSER</literal> clause can be specified to associate a parser
+ plugin with the index if full-text indexing and searching
+ operations need special handling. This clause is legal only for
+ <literal>FULLTEXT</literal> indexes. See
+ <xref linkend="plugin-api"/> for details on creating plugins.
</para>
<para>
- <literal>SPATIAL</literal> indexes can index only spatial
+ <literal>SPATIAL</literal> indexes can include only spatial
columns, and only in <literal>MyISAM</literal> tables. Spatial
column types are described in
<xref linkend="spatial-extensions"/>.
@@ -1440,7 +1448,7 @@
DEFAULT DELAY_KEY_WRITE DELETE DIRECTORY INDEX FIRST FOREIGN
ROW_FORMAT FULL FULLTEXT HEAP INNOBASE INNODB ISAM INSERT_METHOD
MAX_ROWS MIN_ROWS PACK_KEYS PARTIAL MERGE MRG_MYISAM MYISAM NDB
- NDBCLUSTER NO REDUNDANT REFERENCES SERIAL
+ NDBCLUSTER NO REDUNDANT REFERENCES SERIAL WITH PARSER
</remark>
<remark role="help-syntax-begin"/>
@@ -1466,7 +1474,9 @@
| INDEX [<replaceable>index_name</replaceable>] [<replaceable>index_type</replaceable>] (<replaceable>index_col_name</replaceable>,...)
| [CONSTRAINT [<replaceable>symbol</replaceable>]] UNIQUE [INDEX]
[<replaceable>index_name</replaceable>] [<replaceable>index_type</replaceable>] (<replaceable>index_col_name</replaceable>,...)
- | [FULLTEXT|SPATIAL] [INDEX] [<replaceable>index_name</replaceable>] (<replaceable>index_col_name</replaceable>,...)
+ | FULLTEXT [INDEX] [<replaceable>index_name</replaceable>] (<replaceable>index_col_name</replaceable>,...)
+ [WITH PARSER <replaceable>parser_name</replaceable>]
+ | SPATIAL [INDEX] [<replaceable>index_name</replaceable>] (<replaceable>index_col_name</replaceable>,...)
| [CONSTRAINT [<replaceable>symbol</replaceable>]] FOREIGN KEY
[<replaceable>index_name</replaceable>] (<replaceable>index_col_name</replaceable>,...) [<replaceable>reference_definition</replaceable>]
| CHECK (<replaceable>expr</replaceable>)
@@ -2189,7 +2199,13 @@
columns. Indexing always happens over the entire column;
partial indexing is not supported and any prefix length is
ignored if specified. See <xref linkend="fulltext-search"/>
- for details of operation.
+ for details of operation. A <literal>WITH PARSER</literal>
+ clause can be specified to associate a parser plugin with
+ the index if full-text indexing and searching operations
+ need special handling. This clause is legal only for
+ <literal>FULLTEXT</literal> indexes. See
+ <xref linkend="plugin-api"/> for details on creating
+ plugins.
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r553 - in trunk: . refman-5.1 | paul | 13 Dec |
