| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Jan Wieck <JanWieck(at)Yahoo(dot)com>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Peter Childs <Blue(dot)Dragon(at)blueyonder(dot)co(dot)uk>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ADD FOREIGN KEY (was Re: [GENERAL] 7.4Beta) |
| Date: | 2003-09-30 15:15:58 |
| Message-ID: | 19584.1064934958@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2003-09-30 15:29:54 | Re: ADD FOREIGN KEY (was Re: [GENERAL] 7.4Beta) |
| Previous Message | strk | 2003-09-30 15:08:55 | Re: [postgis-users] Union as an aggregate |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2003-09-30 15:29:54 | Re: ADD FOREIGN KEY (was Re: [GENERAL] 7.4Beta) |
| Previous Message | Dave Page | 2003-09-30 15:13:14 | GPL code issue? |