Re: BUG #1770: Composite type dependency broken

From: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
To: David Fetter <david(at)fetter(dot)org>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1770: Composite type dependency broken
Date: 2005-07-15 05:06:52
Message-ID: 20050714220259.D51589@megazone.bigpanda.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, 15 Jul 2005, David Fetter wrote:

> Here's a repro (psql):
>
> create table foo (foo_id SERIAL PRIMARY KEY, foo_text TEXT NOT NULL);
> CREATE type two_foos AS (foo1 foo, foo2 foo);
> CREATE type four_foos AS (two_foo1 two_foos, two_foo2 two_foos);
> DROP TABLE foo CASCADE;
>
> Perhaps I have misunderstood, but I would think that both two_foos and
> four_foos would disappear as a result of this. They don't :/

I think the current definition is that the columns of the removed type
disappear, which means two_foos becomes a type with no columns rather than
it being removed.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2005-07-15 05:26:45 Re: BUG #1770: Composite type dependency broken
Previous Message David Fetter 2005-07-15 01:16:50 Composite Type dependency bug