| From: | Chris Mair <list(at)1006(dot)org> |
|---|---|
| To: | Jasbinder Bali <jsbali(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Triggers in Postgres |
| Date: | 2006-08-01 09:20:39 |
| Message-ID: | 1154424039.4837.3.camel@dell.home.lan |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> http://www.postgresql.org/docs/8.1/interactive/triggers.html
>
> it says something like this:
>
> " It is not currently possible to write a trigger function in the
> plain SQL function language. "
The whole paragraph says.
"It is also possible to write a trigger function in C, although most
people find it easier to use one of the procedural languages. It is not
currently possible to write a trigger function in the plain SQL function
language."
That is: you can and you should write your trigger in a procedural
language. In particular - if you want to stay as closed as possible
to SQL you should use procedural SQL, which in PostgreSQL is called
PL/pgSQL:
http://www.postgresql.org/docs/8.1/interactive/plpgsql.html
Bye, Chris.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Roman Neuhauser | 2006-08-01 11:12:05 | Re: Triggers in Postgres |
| Previous Message | Martijn van Oosterhout | 2006-08-01 09:14:09 | Re: Error in PostgreSQL query with psycopg |