summaryrefslogtreecommitdiffstats
path: root/doc/src/sgml/ref/drop_conversion.sgml
blob: 08558ad7717ba1d20964bb3cadf250809bff08c0 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
<!--
doc/src/sgml/ref/drop_conversion.sgml
PostgreSQL documentation
-->

<refentry id="sql-dropconversion">
 <indexterm zone="sql-dropconversion">
  <primary>DROP CONVERSION</primary>
 </indexterm>

 <refmeta>
  <refentrytitle>DROP CONVERSION</refentrytitle>
  <manvolnum>7</manvolnum>
  <refmiscinfo>SQL - Language Statements</refmiscinfo>
 </refmeta>

 <refnamediv>
  <refname>DROP CONVERSION</refname>
  <refpurpose>remove a conversion</refpurpose>
 </refnamediv>

 <refsynopsisdiv>
<synopsis>
DROP CONVERSION [ IF EXISTS ] <replaceable>name</replaceable> [ CASCADE | RESTRICT ]
</synopsis>
 </refsynopsisdiv>

 <refsect1 id="sql-dropconversion-description">
  <title>Description</title>

  <para>
   <command>DROP CONVERSION</command> removes a previously defined conversion.
   To be able to drop a conversion, you must own the conversion.
  </para>
 </refsect1>

 <refsect1>
  <title>Parameters</title>

   <variablelist>
    <varlistentry>
     <term><literal>IF EXISTS</literal></term>
     <listitem>
      <para>
       Do not throw an error if the conversion does not exist.
       A notice is issued in this case.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><replaceable>name</replaceable></term>

     <listitem>
      <para>
       The name of the conversion. The conversion name can be
       schema-qualified.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><literal>CASCADE</literal></term>
     <term><literal>RESTRICT</literal></term>

     <listitem>
      <para>
       These key words do not have any effect, since there are no
       dependencies on conversions.
      </para>
     </listitem>
    </varlistentry>
   </variablelist>
 </refsect1>

 <refsect1 id="sql-dropconversion-examples">
  <title>Examples</title>

  <para>
   To drop the conversion named <literal>myname</literal>:
<programlisting>
DROP CONVERSION myname;
</programlisting></para>
 </refsect1>

 <refsect1 id="sql-dropconversion-compat">
  <title>Compatibility</title>

  <para>
   There is no <command>DROP CONVERSION</command> statement in the SQL
   standard, but a <command>DROP TRANSLATION</command> statement that
   goes along with the <command>CREATE TRANSLATION</command> statement
   that is similar to the <command>CREATE CONVERSION</command>
   statement in PostgreSQL.
  </para>
 </refsect1>

 <refsect1>
  <title>See Also</title>

  <simplelist type="inline">
   <member><xref linkend="sql-alterconversion"/></member>
   <member><xref linkend="sql-createconversion"/></member>
  </simplelist>
 </refsect1>

</refentry>