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 07:56:38 |
Message-ID: | 7242.1039766198@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Philip Warner <pjw(at)rhyme(dot)com(dot)au> writes:
> At 12:31 AM 13/12/2002 -0500, Tom Lane wrote:
>> 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.
> Seems like a feature - if beth made the type public, she has to deal with
> fame.
But in every other context, Beth has the unconditional right to drop her
type: if it's not the only column in Amy's table, Beth can drop her type
and Amy's column along with it.
Basically, the no-zero-column-tables restriction for deletion was
removed because it creates more weird corner cases than it prevents.
I still agree with that decision. What we're seeing here is that the
corresponding restriction during table creation also creates weird
corner cases.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Philip Warner | 2002-12-13 08:43:37 | Re: Creating a zero-column table |
Previous Message | Tom Lane | 2002-12-13 07:37:21 | Re: Reusing Dead Tuples: |