Re: [HACKERS] Rule system (trigger names)

From: jwieck(at)debis(dot)com (Jan Wieck)
To: andreas(dot)zeugswetter(at)telecom(dot)at (Andreas Zeugswetter)
Cc: jwieck(at)debis(dot)com, hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Rule system (trigger names)
Date: 1998-08-14 09:33:40
Message-ID: m0z7GEu-000EBPC@orion.SAPserv.Hamburg.dsh.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> > possible:
> >
> > CREATE TRIGGER on_insert AFTER INSERT on emp
> > FOR EACH ROW EXECUTE PROCEDURE on_ins_emp();
> >
> > CREATE TRIGGER on_insert AFTER INSERT on payroll
> > FOR EACH ROW EXECUTE PROCEDURE on_ins_payroll();
> >
> > The name of the trigger is the same but the table they
> > triggered for differs and they call different functions.
>
> I think trigger names shoud be unique. Like in Informix, Oracle, DB/2.
>
> Remember to drop a trigger, the syntax usually is:
> drop trigger on_insert;

Not in PostgreSQL. Here it is

DROP TRIGGER trigname ON relation;

>
> so you could safely name the function _trig_<triggername> e.g.
>
> Andreas
>
>
>

Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#======================================== jwieck(at)debis(dot)com (Jan Wieck) #

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Guido Piazzi 1998-08-14 09:36:57 Re: [GENERAL] More details on Database corruption
Previous Message Andreas Zeugswetter 1998-08-14 09:29:44 non instead rule system