mirror of
https://github.com/postgres/postgres.git
synced 2025-11-09 06:21:09 +03:00
6ef2448796
There is what may actually be a mistake in our markup. The problem is in a situation like <para> <command>FOO</command> is ... there is strictly speaking a line break before "FOO". In the HTML output, this does not appear to be a problem, but in the man page output, this shows up, so you get double blank lines at odd places. So far, we have attempted to work around this with an XSL hack, but that causes other problems, such as creating run-ins in places like <acronym>SQL</acronym> <command>COPY</command> So fix the problem properly by removing the extra whitespace. I only fixed the problems that affect the man page output, not all the places.
105 lines
2.5 KiB
Plaintext
105 lines
2.5 KiB
Plaintext
<!-- doc/src/sgml/ref/drop_conversion.sgml -->
|
|
|
|
<refentry id="SQL-DROPCONVERSION">
|
|
<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>
|
|
|
|
<indexterm zone="sql-dropconversion">
|
|
<primary>DROP CONVERSION</primary>
|
|
</indexterm>
|
|
|
|
<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</>:
|
|
<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>
|