| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: Creating a zero-column table |
| Date: | 2002-12-13 05:31:07 |
| Message-ID: | 24043.1039757467@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Philip Warner <pjw(at)rhyme(dot)com(dot)au> writes:
> At 04:08 PM 12/12/2002 -0500, Tom Lane wrote:
>> Should we remove this error check, thereby effectively making
>> zero-column tables first-class citizens?
> The other option is to disallow the steps that resulted in the zero-column
> table in the first place. This is probably more rational.
That was where we were a couple months ago: DROP COLUMN would refuse to
let you drop the last column of a table. But that has much worse
problems than whether we are able to deliver a "helpful" error message.
For example:
Amy does CREATE TABLE foo(f1 beths_type);
Beth now cannot drop her type beths_type.
In most circles this would be called a denial of service.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-12-13 05:31:34 | Re: PQnotifies() in 7.3 broken? |
| Previous Message | Bruce Momjian | 2002-12-13 05:07:07 | Re: PQnotifies() in 7.3 broken? |