Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

alter_text_search_configuration(7) [suse man page]

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)

Check Out this Related Man Page

CREATE TEXT SEARCH 
TEMPLATE(7) SQL Commands CREATE TEXT SEARCH TEMPLATE(7) NAME
CREATE TEXT SEARCH TEMPLATE - define a new text search template SYNOPSIS
CREATE TEXT SEARCH TEMPLATE name ( [ INIT = init_function , ] LEXIZE = lexize_function ) DESCRIPTION
CREATE TEXT SEARCH TEMPLATE creates a new text search template. Text search templates define the functions that implement text search dic- tionaries. A template is not useful by itself, but must be instantiated as a dictionary to be used. The dictionary typically specifies parameters to be given to the template functions. If a schema name is given then the text search template is created in the specified schema. Otherwise it is created in the current schema. You must be a superuser to use CREATE TEXT SEARCH TEMPLATE. This restriction is made because an erroneous text search template definition could confuse or even crash the server. The reason for separating templates from dictionaries is that a template encapsulates the ``unsafe'' aspects of defining a dictionary. The parameters that can be set when defining a dictionary are safe for unprivileged users to set, and so creating a dictionary need not be a privileged operation. Refer to in the documentation for further information. PARAMETERS
name The name of the text search template to be created. The name can be schema-qualified. init_function The name of the init function for the template. lexize_function The name of the lexize function for the template. 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. The lexize function is required, but the init function is optional. The arguments can appear in any order, not only the one shown above. COMPATIBILITY
There is no CREATE TEXT SEARCH TEMPLATE statement in the SQL standard. SEE ALSO
ALTER TEXT SEARCH TEMPLATE [alter_text_search_template(7)], DROP TEXT SEARCH TEMPLATE [drop_text_search_template(7)] SQL - Language Statements 2010-05-14 CREATE TEXT SEARCH TEMPLATE(7)
Man Page

Featured Tech Videos