Re: poll: CHECK TRIGGER?

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема Re: poll: CHECK TRIGGER?
Дата
Msg-id CAFj8pRBHN1ZUFu8ON_yepvuf1TtQDBFAv-ovkOYfYQ+jNChp1A@mail.gmail.com
обсуждение исходный текст
Ответ на Re: poll: CHECK TRIGGER?  (Pavel Stehule <pavel.stehule@gmail.com>)
Ответы Re: poll: CHECK TRIGGER?
Список pgsql-hackers
Hello

>
> When I try to look on some multicheck form:
>
> a) CHECK FUNCTION ALL ON table_name
> b) CHECK TRIGGER ALL ON table_name
>
> then more natural form is @b (for me). Personally, I can live with
> one, both or second form, although I prefer CHECK TRIGGER.
>

I though some time more.

if somebody would to check all custom function, then he can write

CHECK FUNCTION ALL

what about triggers?

CHECK TRIGGER ALL

but if we don't implement CHECK TRIGGER, then this statement will look like

CHECK FUNCTION ALL ON ALL ???

and this is unclean - probably it doesn't mean - check trigger
function with any table. So this is other argument for CREATE TRIGGER.

Nice a day

Pavel


> notes?
>
> Regards
>
> Pavel
>
>
>> --
>> Robert Haas
>> EnterpriseDB: http://www.enterprisedb.com
>> The Enterprise PostgreSQL Company
>>
>> --
>> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-hackers


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Simon Riggs
Дата:
Сообщение: Re: Checksums, state of play
Следующее
От: Noah Misch
Дата:
Сообщение: Re: RFC: Making TRUNCATE more "MVCC-safe"