| From: | Rod Taylor <rbt(at)rbt(dot)ca> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: Cascaded Column Drop |
| Date: | 2002-09-27 04:29:21 |
| Message-ID: | 1033100962.27772.38.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
> > Is that a good idea, or should we refuse the drop entirely? A table
> > drop zaps a lot more stuff than a column drop.
>
> I think we should refuse the drop. It is just too strange. You can
> suggest if they want the column dropped, just drop the table.
Leaving a zero-width table would be best, even if its not so useful. I
don't like rejecting a CASCADE as it kinda defeats the purpose of having
CASCADE.
The patch may not work right in complex cases anyway. It seems the
switch to remove the table should be earlier.
--
Rod Taylor
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Mercer | 2002-09-27 04:31:48 | Re: hacker help: PHP-4.2.3 patch to allow restriction of database access |
| Previous Message | Tatsuo Ishii | 2002-09-27 04:29:19 | Re: unicode |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-09-27 04:46:33 | Re: one last patch - array lower and upper bound |
| Previous Message | Tom Lane | 2002-09-27 04:28:56 | Re: Cascaded Column Drop |