From: | "Jim C(dot) Nasby" <decibel(at)decibel(dot)org> |
---|---|
To: | Hannu Krosing <hannu(at)tm(dot)ee> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Shortcut for defining triggers |
Date: | 2005-01-25 21:49:45 |
Message-ID: | 20050125214945.GZ67721@decibel.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jan 24, 2005 at 10:50:13AM +0200, Hannu Krosing wrote:
> ?hel kenal p?eval (p?hap?ev, 23. jaanuar 2005, 15:49-0600), kirjutas Jim
> C. Nasby:
> > Sorry if this is old, but I couldn't find it in the archives...
> >
> > How difficult would it be to provide a means to define a trigger in one
> > statement? Something like a combination of CREATE TRIGGER and CREATE
> > FUNCTION? Being able to define them seperately is awesome for generic
> > cases where you can use one function for a bunch of different tables,
> > but it's a pain in the cases where you need a unique trigger for one
> > table.
>
> The same is true for the need to define RETURN TYPE of a function
> separately from the function.
>
> So: How difficult would it be to provide a means to define a function
> and its return type in one statement?
I'm sorry, I must be missing something... if you're defining a trigger
without seperately defining a function for it, why do you need to worry
about the return type of anything?
--
Jim C. Nasby, Database Consultant decibel(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828
Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2005-01-25 21:52:48 | Re: Shortcut for defining triggers |
Previous Message | Tom Lane | 2005-01-25 21:47:11 | Re: Autotuning Group Commit |