| From: | Bill <pg(at)dbginc(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PgSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Trigger function is not called |
| Date: | 2008-08-26 00:20:48 |
| Message-ID: | 48B34C60.4090306@dbginc.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
You'd have the same problem. By the time the trigger sees it, the row
> has already been converted to the table's column datatype(s), so any
> exception associated with a datatype or domain would be thrown already.
>
> A lot of people seem to have trouble with this concept; I dunno what
> data representation they think the trigger is working on...
>
> If you want to enforce constraints for a table in the trigger, you can
> do that, but it's not going to work to try to mix and match
> trigger-based and datatype-based restrictions.
>
> regards, tom lane
>
>
>
I have no problem with the concept now that I understand it. It is just
different than InterBase and Firebird which I have done a lot of work
with lately. Thanks very much for your help.
Bill
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Phoenix Kiula | 2008-08-26 01:25:09 | Re: Easy upgrade on Cpanel *without* downtime |
| Previous Message | Tom Lane | 2008-08-26 00:11:38 | Re: Trigger function is not called |