| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Richard Broersma <richard(dot)broersma(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: CREATE CONSTRAINT TRIGGER |
| Date: | 2010-11-09 19:57:49 |
| Message-ID: | 1289332641-sup-252@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Richard Broersma's message of vie nov 05 18:54:54 -0300 2010:
> On Fri, Nov 5, 2010 at 2:37 PM, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
>
> > Recent developments have turned it back into non-deprecated mode; it's
> > not going anywhere, and it needs to be fully documented.
>
> From what I recall, there isn't anything in the trigger documentation
> or CREATE CONSTRAINT TRIGGER documentation that says the trigger
> function must explicitly raise an exception to create the notification
> that the custom constraint was violated.
>
>
> Would this be a good place for it?
I added a sentence about this, and pushed it.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2010-11-09 20:02:21 | Re: proposal: plpgsql - iteration over fields of rec or row variable |
| Previous Message | Merlin Moncure | 2010-11-09 19:41:32 | Re: proposal: plpgsql - iteration over fields of rec or row variable |