Re: BUG #1770: Composite type dependency broken - Mailing list pgsql-bugs

From Stephan Szabo
Subject Re: BUG #1770: Composite type dependency broken
Date
Msg-id 20050714220259.D51589@megazone.bigpanda.com
Whole thread Raw
In response to BUG #1770: Composite type dependency broken  ("David Fetter" <david@fetter.org>)
List 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.

pgsql-bugs by date:

Previous
From: "David Fetter"
Date:
Subject: BUG #1770: Composite type dependency broken
Next
From: Tom Lane
Date:
Subject: Re: BUG #1770: Composite type dependency broken