From: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | "Mike Mascari" <mascarm(at)mascari(dot)com> |
Cc: | "Don Baccus" <dhogaza(at)pacifier(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "PostgreSQL Development" <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | RE: [HACKERS] Happy column dropping |
Date: | 2000-01-25 07:18:22 |
Message-ID: | 001401bf6704$5ca7e3a0$2801007e@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> -----Original Message-----
> From: Mike Mascari [mailto:mascarm(at)mascari(dot)com]
>
> >
> > Do other DBMSs allow such things ?
> > For example,in Oracle NOT NULL constraint could be specified for new
> > column only when there's no row in the table AFAIK.
> >
> > I couldn't judge it's worth the work.
> >
>
> But the times when I've found it would be nice to use ALTER TABLE
> ADD COLUMN with NOT NULL constraints is in development mode when
> the schema is changing rapidly and there actually isn't any data
> yet in the tables. Otherwise, to add a new NOT NULL column during
> a development cycle, one has to drop and recreate the table, all
> triggers, comments, etc. Its just a real pain. :-(
>
I don't know details about constraints.
Probably you could implement it better than me.
Even default is not allowed in ADD COLUMN now.
There may be other reasons why they aren't allowed.
Regards.
Hiroshi Inoue
Inoue(at)tpf(dot)co(dot)jp
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Mascari | 2000-01-25 07:24:10 | Re: [HACKERS] Happy column dropping |
Previous Message | Adriaan Joubert | 2000-01-25 07:15:41 | Re: [HACKERS] DISTINCT ON: speak now or forever hold your peace |