Why Gemfury? Push, build, and install  RubyGems npm packages Python packages Maven artifacts PHP packages Go Modules Debian packages RPM packages NuGet packages

Repository URL to install this package:

Details    
postgresql96-docs / usr / share / doc / postgresql96-docs-9.6.1 / sgml / ref / drop_trigger.sgml
Size: Mime:
<!--
doc/src/sgml/ref/drop_trigger.sgml
PostgreSQL documentation
-->

<refentry id="SQL-DROPTRIGGER">
 <indexterm zone="sql-droptrigger">
  <primary>DROP TRIGGER</primary>
 </indexterm>

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

 <refnamediv>
  <refname>DROP TRIGGER</refname>
  <refpurpose>remove a trigger</refpurpose>
 </refnamediv>

 <refsynopsisdiv>
<synopsis>
DROP TRIGGER [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable> ON <replaceable class="PARAMETER">table_name</replaceable> [ CASCADE | RESTRICT ]
</synopsis>
 </refsynopsisdiv>

 <refsect1>
  <title>Description</title>

  <para>
   <command>DROP TRIGGER</command> removes an existing
   trigger definition. To execute this command, the current
   user must be the owner of the table for which the trigger is defined.
  </para>
 </refsect1>

 <refsect1>
  <title>Parameters</title>

  <variablelist>

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

   <varlistentry>
    <term><replaceable class="PARAMETER">name</replaceable></term>
    <listitem>
     <para>
      The name of the trigger to remove.
     </para>
    </listitem>
   </varlistentry>

   <varlistentry>
    <term><replaceable class="PARAMETER">table_name</replaceable></term>
    <listitem>
     <para>
      The name (optionally schema-qualified) of the table for which
      the trigger is defined.
     </para>
    </listitem>
   </varlistentry>

   <varlistentry>
    <term><literal>CASCADE</literal></term>
    <listitem>
     <para>
      Automatically drop objects that depend on the trigger,
      and in turn all objects that depend on those objects
      (see <xref linkend="ddl-depend">).
     </para>
    </listitem>
   </varlistentry>

   <varlistentry>
    <term><literal>RESTRICT</literal></term>
    <listitem>
     <para>
      Refuse to drop the trigger if any objects depend on it.  This is
      the default.
     </para>
    </listitem>
   </varlistentry>
  </variablelist>
 </refsect1>

 <refsect1 id="SQL-DROPTRIGGER-examples">
  <title>Examples</title>

  <para>
   Destroy the trigger <literal>if_dist_exists</literal> on the table
   <literal>films</literal>:

<programlisting>
DROP TRIGGER if_dist_exists ON films;
</programlisting></para>
 </refsect1>

 <refsect1 id="SQL-DROPTRIGGER-compatibility">
  <title>Compatibility</title>

  <para>
   The <command>DROP TRIGGER</command> statement in
   <productname>PostgreSQL</productname> is incompatible with the SQL
   standard.  In the SQL standard, trigger names are not local to
   tables, so the command is simply <literal>DROP TRIGGER
   <replaceable>name</replaceable></literal>.
  </para>
 </refsect1>

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

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

</refentry>