Re: ADD FOREIGN KEY (was Re: [GENERAL] 7.4Beta)
От | Tom Lane |
---|---|
Тема | Re: ADD FOREIGN KEY (was Re: [GENERAL] 7.4Beta) |
Дата | |
Msg-id | 19584.1064934958@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: ADD FOREIGN KEY (was Re: [GENERAL] 7.4Beta) (Stephan Szabo <sszabo@megazone.bigpanda.com>) |
Ответы |
Re: ADD FOREIGN KEY (was Re: [GENERAL] 7.4Beta)
|
Список | pgsql-hackers |
Stephan Szabo <sszabo@megazone.bigpanda.com> writes: > As a side note, in the partial implementation I'd already done, I noticed > a potential problem if the person doing the alter table didn't have read > permissions on the pktable. I'd written it to bail and do the slow check > in that case (well actually in most error cases that didn't themselves > cause an elog), does anyone have a better idea? Wouldn't all the subsequent triggers fail also in such a case? (For that matter, wouldn't the existing implementation of the initial check fail?) I can't see a reason to expend code to avoid failing here. It's not very sensible to be able to create an FK on a table you don't have read permission for. regards, tom lane
В списке pgsql-hackers по дате отправления: