| From: | Richard Broersma <richard(dot)broersma(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: CREATE CONSTRAINT TRIGGER |
| Date: | 2010-11-05 21:54:54 |
| Message-ID: | AANLkTinqYYtpQcXaDaniHfn-j8u67goGp4yUALPkvd4E@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
--
Regards,
Richard Broersma Jr.
Visit the Los Angeles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-11-05 22:03:20 | Re: Query Plan Columns |
| Previous Message | Greg Smith | 2010-11-05 21:53:37 | Re: [PATCH] Revert default wal_sync_method to fdatasync on Linux 2.6.33+ |