Re: Trigger function is not called

Поиск
Список
Период
Сортировка
Искать
От
Tom Lane
Тема
Re: Trigger function is not called
Дата
Msg-id
9830.1219709498@sss.pgh.pa.us
Ответ на
Список
Дерево обсуждения
Trigger function is not called Bill <pg@dbginc.com>
Re: Trigger function is not called Tom Lane <tgl@sss.pgh.pa.us>
Re: Trigger function is not called Bill <pg@dbginc.com>
Re: Trigger function is not called Tom Lane <tgl@sss.pgh.pa.us>
Re: Trigger function is not called Bill <pg@dbginc.com>
Re: Trigger function is not called Tom Lane <tgl@sss.pgh.pa.us>
Re: Trigger function is not called Bill <pg@dbginc.com>
Re: Trigger function is not called Bill <pg@dbginc.com>
Re: Trigger function is not called Tom Lane <tgl@sss.pgh.pa.us>
Re: Trigger function is not called Bill <pg@dbginc.com>
Re: Trigger function is not called Tom Lane <tgl@sss.pgh.pa.us>
Re: Trigger function is not called Bill <pg@dbginc.com>
Re: Trigger function is not called Klint Gore <kgore4@une.edu.au>
Re: Trigger function is not called Tom Lane <tgl@sss.pgh.pa.us>
Bill  writes:
> Is it possible to create a type and use that instead of the domain or 
> will I have the same problem with a type?

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
В списке pgsql-general по дате отправления
От: Bill
Дата:
От: Bill
Дата:
FAQ