drop_conversion(7) [redhat man page]

DROP 
CONVERSION(7)						   SQL Commands 						DROP CONVERSION(7)

NAME

       DROP CONVERSION - remove a user-defined conversion

SYNOPSIS

       DROP CONVERSION conversion_name
	   [ CASCADE | RESTRICT ]

DESCRIPTION

       DROP CONVERSION removes a previously defined conversion.

       To be able to drop a conversion, you must own the conversion.  "PARAMETERS"

       conversion_name
	      The name of the conversion. The conversion name may be schema-qualified.

       CASCADE

       RESTRICT
	      These key words do not have any effect, since there are no dependencies on conversions.

NOTES

       Use CREATE CONVERSION to create user-defined conversions.

       The privileges required to drop a conversion may be changed in a future release.

EXAMPLES

       To drop the conversion named myname:

       DROP CONVERSION myname;

COMPATIBILITY

       DROP CONVERSION is a PostgreSQL extension.  There is no DROP CONVERSION statement in SQL99.

SEE ALSO

       CREATE CONVERSION [create_conversion(7)]

SQL - Language Statements					    2002-11-22							DROP CONVERSION(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)