From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Rod Taylor <rbt(at)rbt(dot)ca> |
Cc: | PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Cascaded Column Drop |
Date: | 2002-09-27 03:47:08 |
Message-ID: | 20660.1033098428@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Rod Taylor <rbt(at)rbt(dot)ca> writes:
> When a cascaded column drop is removing the last column, drop the table
> instead. Regression tests via domains.
Is that a good idea, or should we refuse the drop entirely? A table
drop zaps a lot more stuff than a column drop.
What I was actually wondering about after reading Tim's report was
whether we could support zero-column tables, which would eliminate the
need for the special case altogether. I have not looked to see how
extensive are the places that assume tuples have > 0 columns ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-09-27 03:58:20 | Re: postmaster -d option (was Re: [GENERAL] Relation 0 does |
Previous Message | Tom Lane | 2002-09-27 03:42:44 | Re: hacker help: PHP-4.2.3 patch to allow restriction of database access |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-09-27 04:00:47 | Re: Cascaded Column Drop |
Previous Message | Gavin Sherry | 2002-09-27 01:29:57 | Re: additional patch for contrib/tablefunc - added to |