On Monday December 6 2004 11:50, Tom Lane wrote:
> "Ed L." <[EMAIL PROTECTED]> 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
> >
"Ed L." <[EMAIL PROTECTED]> 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 d
On Monday December 6 2004 9:45, Ed L. wrote:
> On Sun, 05 Dec 2004 14:54:38, Tom Lane wrote:
> > On Sunday December 5 2004 12:34, Ed L. wrote:
> > > The following queries result in a dropped sequence, but IMO should
> > > not:
> > >
> > > create table foo(id serial);
> > > create table bar(id integ
On Sun, 05 Dec 2004 14:54:38, Tom Lane wrote:
> On Sunday December 5 2004 12:34, Ed L. wrote:
> > The following queries result in a dropped sequence, but IMO should not:
> >
> > create table foo(id serial);
> > create table bar(id integer not null nextval('foo_id_seq'::text));
> > alter table foo a
"Ed L." <[EMAIL PROTECTED]> writes:
> The following queries result in a dropped sequence, but IMO should not:
> create table foo(id serial);
> create table bar(id integer not null nextval('foo_id_seq'::text));
> alter table foo alter column id drop default;
> drop table foo;
I don't think that fo
The following queries result in a dropped sequence, but IMO should not:
create table foo(id serial);
create table bar(id integer not null nextval('foo_id_seq'::text));
alter table foo alter column id drop default;
drop table foo;
Once dependence between foo and foo_id_seq has been removed, a dro
