drop_language(7) [redhat man page]

DROP 
LANGUAGE(7)						   SQL Commands 						  DROP LANGUAGE(7)

NAME

       DROP LANGUAGE - remove a user-defined procedural language

SYNOPSIS

       DROP [ PROCEDURAL ] LANGUAGE name [ CASCADE | RESTRICT ]

   INPUTS
       name   The name of an existing procedural language. For backward compatibility, the name may be enclosed by single quotes.

       CASCADE
	      Automatically drop objects that depend on the language (such as functions in the language).

       RESTRICT
	      Refuse to drop the language if there are any dependent objects.  This is the default.

   OUTPUTS
       DROP LANGUAGE
	      This message is returned if the language is successfully dropped.

       ERROR: Language "name" doesn't exist
	      This message occurs if a language called name is not found in the database.

DESCRIPTION

       DROP PROCEDURAL LANGUAGE will remove the definition of the previously registered procedural language called name.

   NOTES
       The DROP PROCEDURAL LANGUAGE statement is a PostgreSQL language extension.

       Refer to CREATE LANGUAGE [create_language(7)] for information on how to create procedural languages.

USAGE

       This command removes the PL/Sample language:

       DROP LANGUAGE plsample;

COMPATIBILITY

   SQL92
       There is no DROP PROCEDURAL LANGUAGE in SQL92.

SQL - Language Statements					    2002-11-22							  DROP LANGUAGE(7)

DROP 
TRIGGER(7) 						   SQL Commands 						   DROP TRIGGER(7)

NAME

       DROP TRIGGER - remove a trigger

SYNOPSIS

       DROP TRIGGER name ON table [ CASCADE | RESTRICT ]

   INPUTS
       name   The name of an existing trigger.

       table  The name (optionally schema-qualified) of a table.

       CASCADE
	      Automatically drop objects that depend on the trigger.

       RESTRICT
	      Refuse to drop the trigger if there are any dependent objects.  This is the default.

   OUTPUTS
       DROP TRIGGER
	      The message returned if the trigger is successfully dropped.

       ERROR: DropTrigger: there is no trigger name on relation "table"
	      This message occurs if the trigger specified does not exist.

DESCRIPTION

       DROP  TRIGGER will remove an existing trigger definition. To execute this command the current user must be the owner of the table for which
       the trigger is defined.

EXAMPLES

       Destroy the if_dist_exists trigger on table films:

       DROP TRIGGER if_dist_exists ON films;

COMPATIBILITY

       SQL92  There is no DROP TRIGGER statement in SQL92.

       SQL99  The DROP TRIGGER statement in PostgreSQL is incompatible with SQL99. In SQL99, trigger names are not local to tables, so the command
	      is simply DROP TRIGGER name.

SEE ALSO

       CREATE TRIGGER [create_trigger(7)]

SQL - Language Statements					    2002-11-22							   DROP TRIGGER(7)