| 1 |
<!-- |
| 2 |
doc/src/sgml/ref/drop_conversion.sgml |
| 3 |
PostgreSQL documentation |
| 4 |
--> |
| 5 |
|
| 6 |
<refentry id="sql-dropconversion"> |
| 7 |
<indexterm zone="sql-dropconversion"> |
| 8 |
<primary>DROP CONVERSION</primary> |
| 9 |
</indexterm> |
| 10 |
|
| 11 |
<refmeta> |
| 12 |
<refentrytitle>DROP CONVERSION</refentrytitle> |
| 13 |
<manvolnum>7</manvolnum> |
| 14 |
<refmiscinfo>SQL - Language Statements</refmiscinfo> |
| 15 |
</refmeta> |
| 16 |
|
| 17 |
<refnamediv> |
| 18 |
<refname>DROP CONVERSION</refname> |
| 19 |
<refpurpose>remove a conversion</refpurpose> |
| 20 |
</refnamediv> |
| 21 |
|
| 22 |
<refsynopsisdiv> |
| 23 |
<synopsis> |
| 24 |
DROP CONVERSION [ IF EXISTS ] <replaceable>name</replaceable> [ CASCADE | RESTRICT ] |
| 25 |
</synopsis> |
| 26 |
</refsynopsisdiv> |
| 27 |
|
| 28 |
<refsect1 id="sql-dropconversion-description"> |
| 29 |
<title>Description</title> |
| 30 |
|
| 31 |
<para> |
| 32 |
<command>DROP CONVERSION</command> removes a previously defined conversion. |
| 33 |
To be able to drop a conversion, you must own the conversion. |
| 34 |
</para> |
| 35 |
</refsect1> |
| 36 |
|
| 37 |
<refsect1> |
| 38 |
<title>Parameters</title> |
| 39 |
|
| 40 |
<variablelist> |
| 41 |
<varlistentry> |
| 42 |
<term><literal>IF EXISTS</literal></term> |
| 43 |
<listitem> |
| 44 |
<para> |
| 45 |
Do not throw an error if the conversion does not exist. |
| 46 |
A notice is issued in this case. |
| 47 |
</para> |
| 48 |
</listitem> |
| 49 |
</varlistentry> |
| 50 |
|
| 51 |
<varlistentry> |
| 52 |
<term><replaceable>name</replaceable></term> |
| 53 |
|
| 54 |
<listitem> |
| 55 |
<para> |
| 56 |
The name of the conversion. The conversion name can be |
| 57 |
schema-qualified. |
| 58 |
</para> |
| 59 |
</listitem> |
| 60 |
</varlistentry> |
| 61 |
|
| 62 |
<varlistentry> |
| 63 |
<term><literal>CASCADE</literal></term> |
| 64 |
<term><literal>RESTRICT</literal></term> |
| 65 |
|
| 66 |
<listitem> |
| 67 |
<para> |
| 68 |
These key words do not have any effect, since there are no |
| 69 |
dependencies on conversions. |
| 70 |
</para> |
| 71 |
</listitem> |
| 72 |
</varlistentry> |
| 73 |
</variablelist> |
| 74 |
</refsect1> |
| 75 |
|
| 76 |
<refsect1 id="sql-dropconversion-examples"> |
| 77 |
<title>Examples</title> |
| 78 |
|
| 79 |
<para> |
| 80 |
To drop the conversion named <literal>myname</literal>: |
| 81 |
<programlisting> |
| 82 |
DROP CONVERSION myname; |
| 83 |
</programlisting></para> |
| 84 |
</refsect1> |
| 85 |
|
| 86 |
<refsect1 id="sql-dropconversion-compat"> |
| 87 |
<title>Compatibility</title> |
| 88 |
|
| 89 |
<para> |
| 90 |
There is no <command>DROP CONVERSION</command> statement in the SQL |
| 91 |
standard, but a <command>DROP TRANSLATION</command> statement that |
| 92 |
goes along with the <command>CREATE TRANSLATION</command> statement |
| 93 |
that is similar to the <command>CREATE CONVERSION</command> |
| 94 |
statement in PostgreSQL. |
| 95 |
</para> |
| 96 |
</refsect1> |
| 97 |
|
| 98 |
<refsect1> |
| 99 |
<title>See Also</title> |
| 100 |
|
| 101 |
<simplelist type="inline"> |
| 102 |
<member><xref linkend="sql-alterconversion"/></member> |
| 103 |
<member><xref linkend="sql-createconversion"/></member> |
| 104 |
</simplelist> |
| 105 |
</refsect1> |
| 106 |
|
| 107 |
</refentry> |