From: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: serial drop error |
Date: | 2004-12-06 20:43:35 |
Message-ID: | 200412061343.35671.pgsql@bluepolka.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Monday December 6 2004 11:50, Tom Lane wrote:
> "Ed L." <pgsql(at)bluepolka(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Belbin, Peter | 2004-12-06 22:43:26 | solaris 10 with gcc 3.3.2 |
Previous Message | Michael Meskes | 2004-12-06 20:28:43 | Re: BUG #1292: ecpg precompile bug (valiable typedef & define ) |