Re: serial drop error - Mailing list pgsql-bugs

From Ed L.
Subject Re: serial drop error
Date
Msg-id 200412061343.35671.pgsql@bluepolka.net
Whole thread Raw
In response to Re: serial drop error  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Monday December 6 2004 11:50, Tom Lane wrote:
> "Ed L." <pgsql@bluepolka.net> writes:
> > I can see the point of *not* dropping the sequence unless the
> > owning column is dropped.  I just don't see the point of disabling the
> > useful ability to decouple the sequence-column association, and
> > dropping the default seems the most reasonable way to do that.
>
> Where we part ways is on the claim that this is useful.  As I said
> before, if you think they are independent objects then you should create
> 'em that way.

What was I thinking??  I so agree, this would be useless capability for
existing tables.  Being able to decouple the sequence/table dependency is
only ever useful in the absence of foresight to have avoided use of SERIAL
in the first place.  If one lacks that foresight, that's just too bad, they
can just find another way.

Ed

pgsql-bugs by date:

Previous
From: Michael Meskes
Date:
Subject: Re: BUG #1292: ecpg precompile bug (valiable typedef & define )
Next
From: Frank van Vugt
Date:
Subject: Re: "invalid memory alloc request size " in deferred trigger causes transaction to fail, but the backend keeps running