From 6eb9c5a5657d1fe77b55cc261450f3538d35a94d Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 4 May 2024 14:19:15 +0200 Subject: Adding upstream version 13.4. Signed-off-by: Daniel Baumann --- doc/src/sgml/ref/drop_conversion.sgml | 107 ++++++++++++++++++++++++++++++++++ 1 file changed, 107 insertions(+) create mode 100644 doc/src/sgml/ref/drop_conversion.sgml (limited to 'doc/src/sgml/ref/drop_conversion.sgml') diff --git a/doc/src/sgml/ref/drop_conversion.sgml b/doc/src/sgml/ref/drop_conversion.sgml new file mode 100644 index 0000000..08558ad --- /dev/null +++ b/doc/src/sgml/ref/drop_conversion.sgml @@ -0,0 +1,107 @@ + + + + + DROP CONVERSION + + + + DROP CONVERSION + 7 + SQL - Language Statements + + + + DROP CONVERSION + remove a conversion + + + + +DROP CONVERSION [ IF EXISTS ] name [ CASCADE | RESTRICT ] + + + + + Description + + + DROP CONVERSION removes a previously defined conversion. + To be able to drop a conversion, you must own the conversion. + + + + + Parameters + + + + IF EXISTS + + + Do not throw an error if the conversion does not exist. + A notice is issued in this case. + + + + + + name + + + + The name of the conversion. The conversion name can be + schema-qualified. + + + + + + CASCADE + RESTRICT + + + + These key words do not have any effect, since there are no + dependencies on conversions. + + + + + + + + Examples + + + To drop the conversion named myname: + +DROP CONVERSION myname; + + + + + Compatibility + + + There is no DROP CONVERSION statement in the SQL + standard, but a DROP TRANSLATION statement that + goes along with the CREATE TRANSLATION statement + that is similar to the CREATE CONVERSION + statement in PostgreSQL. + + + + + See Also + + + + + + + + -- cgit v1.2.3