From 46651ce6fe013220ed397add242004d764fc0153 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 4 May 2024 14:15:05 +0200 Subject: Adding upstream version 14.5. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/sql-droptsparser.html | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 doc/src/sgml/html/sql-droptsparser.html (limited to 'doc/src/sgml/html/sql-droptsparser.html') diff --git a/doc/src/sgml/html/sql-droptsparser.html b/doc/src/sgml/html/sql-droptsparser.html new file mode 100644 index 0000000..2982e55 --- /dev/null +++ b/doc/src/sgml/html/sql-droptsparser.html @@ -0,0 +1,32 @@ + +DROP TEXT SEARCH PARSER
DROP TEXT SEARCH PARSER
Prev UpSQL CommandsHome Next

DROP TEXT SEARCH PARSER

DROP TEXT SEARCH PARSER — remove a text search parser

Synopsis

+DROP TEXT SEARCH PARSER [ IF EXISTS ] name [ CASCADE | RESTRICT ]
+

Description

+ DROP TEXT SEARCH PARSER drops an existing text search + parser. You must be a superuser to use this command. +

Parameters

IF EXISTS

+ Do not throw an error if the text search parser does not exist. + A notice is issued in this case. +

name

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

CASCADE

+ Automatically drop objects that depend on the text search parser, + and in turn all objects that depend on those objects + (see Section 5.14). +

RESTRICT

+ Refuse to drop the text search parser if any objects depend on it. + This is the default. +

Examples

+ Remove the text search parser my_parser: + +

+DROP TEXT SEARCH PARSER my_parser;
+

+ + This command will not succeed if there are any existing text search + configurations that use the parser. Add CASCADE to + drop such configurations along with the parser. +

Compatibility

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

Prev Up Next
DROP TEXT SEARCH DICTIONARY Home DROP TEXT SEARCH TEMPLATE
\ No newline at end of file -- cgit v1.2.3