From: | "Jonathan M(dot) Gardner" <jgardner(at)jonathangardner(dot)net> |
---|---|
To: | <phil(at)cobol-africa(dot)com> |
Cc: | <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: Triggers |
Date: | 2004-03-05 16:32:37 |
Message-ID: | 200403050832.40529.jgardner@jonathangardner.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday 26 February 2004 2:18 am, Philip J. Boonzaaier wrote:
> The technical reference gives an example of a trigger on a table -
> employee Just to test this, I have created the following table,
> CREATE TABLE employee
> (name VARCHAR(30),
> age int4,
> state VARCHAR(2),
> manager VARCHAR(3),
> adult VARCHAR(3));
>
> The I created a simple Function, as follows :
>
> CREATE FUNCTION trig_insert_update_check_emp() RETURNS opaque AS '
> BEGIN
> IF new.age > 20 THEN
> new.adult = ''yes'';
> ELSE
> new.adult = ''no'';
> END IF;
> END;
> ' LANGUAGE 'plpgsql';
Couple of comments:
1) Your trigger functions needs to return something. In this case, you
would "RETURN NEW".
2) I believe trigger functions need to "RETURNS TRIGGER", not "RETURNS
opaque", but I could be wrong. Give that a try.
Question:
1) What version of PostgreSQL are you running?
- --
Jonathan Gardner
jgardner(at)jonathangardner(dot)net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFASKulqp6r/MVGlwwRAgpLAKCycwL/i+/mb6bW1W4QjHKBO9e0xQCgl42q
pmohSw7PZiuIWgOQXxtgvI0=
=4iDJ
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Jonathan M. Gardner | 2004-03-05 16:39:12 | Re: VIEW on lookup table |
Previous Message | Jonathan M. Gardner | 2004-03-05 16:28:42 | Re: query optimization |