create_text_search_parser(7) [suse man page]

CREATE TEXT SEARCH 
PARSER(7)					   SQL Commands 				      CREATE TEXT SEARCH PARSER(7)

NAME

       CREATE TEXT SEARCH PARSER - define a new text search parser

SYNOPSIS

       CREATE TEXT SEARCH PARSER name (
	   START = start_function ,
	   GETTOKEN = gettoken_function ,
	   END = end_function ,
	   LEXTYPES = lextypes_function
	   [, HEADLINE = headline_function ]
       )

DESCRIPTION

       CREATE  TEXT  SEARCH PARSER creates a new text search parser. A text search parser defines a method for splitting a text string into tokens
       and assigning types (categories) to the tokens.	A parser is not particularly useful by itself, but must be bound into a text  search  con-
       figuration along with some text search dictionaries to be used for searching.

       If a schema name is given then the text search parser is created in the specified schema. Otherwise it is created in the current schema.

       You  must  be  a  superuser to use CREATE TEXT SEARCH PARSER.  (This restriction is made because an erroneous text search parser definition
       could confuse or even crash the server.)

       Refer to in the documentation for further information.

PARAMETERS

       name   The name of the text search parser to be created. The name can be schema-qualified.

       start_function
	      The name of the start function for the parser.

       gettoken_function
	      The name of the get-next-token function for the parser.

       end_function
	      The name of the end function for the parser.

       lextypes_function
	      The name of the lextypes function for the parser (a function that returns information about the set of token types it produces).

       headline_function
	      The name of the headline function for the parser (a function that summarizes a set of tokens).

       The function names can be schema-qualified if necessary. Argument types are not given, since the argument list for each type of function is
       predetermined. All except the headline function are required.

       The arguments can appear in any order, not only the one shown above.

COMPATIBILITY

       There is no CREATE TEXT SEARCH PARSER statement in the SQL standard.

SEE ALSO

       ALTER TEXT SEARCH PARSER [alter_text_search_parser(7)], DROP TEXT SEARCH PARSER [drop_text_search_parser(7)]

SQL - Language Statements					    2010-05-14					      CREATE TEXT SEARCH PARSER(7)

ALTER TEXT SEARCH 
CONFIGURATION(7)				   SQL Commands 				ALTER TEXT SEARCH CONFIGURATION(7)

NAME

       ALTER TEXT SEARCH CONFIGURATION - change the definition of a text search configuration

SYNOPSIS

       ALTER TEXT SEARCH CONFIGURATION name
	   ADD MAPPING FOR token_type [, ... ] WITH dictionary_name [, ... ]
       ALTER TEXT SEARCH CONFIGURATION name
	   ALTER MAPPING FOR token_type [, ... ] WITH dictionary_name [, ... ]
       ALTER TEXT SEARCH CONFIGURATION name
	   ALTER MAPPING REPLACE old_dictionary WITH new_dictionary
       ALTER TEXT SEARCH CONFIGURATION name
	   ALTER MAPPING FOR token_type [, ... ] REPLACE old_dictionary WITH new_dictionary
       ALTER TEXT SEARCH CONFIGURATION name
	   DROP MAPPING [ IF EXISTS ] FOR token_type [, ... ]
       ALTER TEXT SEARCH CONFIGURATION name RENAME TO newname
       ALTER TEXT SEARCH CONFIGURATION name OWNER TO newowner

DESCRIPTION

       ALTER TEXT SEARCH CONFIGURATION changes the definition of a text search configuration. You can modify its mappings from token types to dic-
       tionaries, or change the configuration's name or owner.

       You must be the owner of the configuration to use ALTER TEXT SEARCH CONFIGURATION.

PARAMETERS

       name   The name (optionally schema-qualified) of an existing text search configuration.

       token_type
	      The name of a token type that is emitted by the configuration's parser.

       dictionary_name
	      The name of a text search dictionary to be consulted for the specified token type(s). If multiple dictionaries are listed, they  are
	      consulted in the specified order.

       old_dictionary
	      The name of a text search dictionary to be replaced in the mapping.

       new_dictionary
	      The name of a text search dictionary to be substituted for old_dictionary.

       newname
	      The new name of the text search configuration.

       newowner
	      The new owner of the text search configuration.

       The  ADD  MAPPING  FOR  form  installs  a  list of dictionaries to be consulted for the specified token type(s); it is an error if there is
       already a mapping for any of the token types.  The ALTER MAPPING FOR form does the same, but first removing any existing mapping for  those
       token  types.   The ALTER MAPPING REPLACE forms substitute new_dictionary for old_dictionary anywhere the latter appears.  This is done for
       only the specified token types when FOR appears, or for all mappings of the configuration when it doesn't.  The DROP MAPPING  form  removes
       all  dictionaries  for  the specified token type(s), causing tokens of those types to be ignored by the text search configuration. It is an
       error if there is no mapping for the token types, unless IF EXISTS appears.

EXAMPLES

       The following example replaces the english dictionary with the swedish dictionary anywhere that english is used within my_config.

       ALTER TEXT SEARCH CONFIGURATION my_config
	 ALTER MAPPING REPLACE english WITH swedish;

COMPATIBILITY

       There is no ALTER TEXT SEARCH CONFIGURATION statement in the SQL standard.

SEE ALSO

       CREATE TEXT SEARCH CONFIGURATION [create_text_search_configuration(7)], DROP TEXT SEARCH CONFIGURATION [drop_text_search_configuration(7)]

SQL - Language Statements					    2010-05-14					ALTER TEXT SEARCH CONFIGURATION(7)