Re: Default values for nulls not being set.

From: "Donald Fraser" <demolish(at)cwgsy(dot)net>
To: "[BUGS]" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Default values for nulls not being set.
Date: 2003-03-04 11:01:47
Message-ID: 001001c2e23d$76713bd0$1664a8c0@DEMOLITION
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


> "Donald Fraser" <demolish(at)cwgsy(dot)net> writes:
> > I have a major problem with DEAFAULT values:
>
> Consider attaching a default to the view column. As-is, its default
> is NULL (and I can't see any good argument for the factory default
> being anything else).

What would be nice is when you don't specify a default on the view, the default
from the table is used.
That way, for most cases, you would only need to specify the default in one
place and not for every view...

regards Don.

> tt=# INSERT INTO vu_tbl_test (id, s_desc) VALUES('2', 'View insert test');
> ERROR: ExecInsert: Fail to add null value in not null attribute b_disabled
> tt=# alter table vu_tbl_test alter column b_disabled set default '0';
> ALTER TABLE
> tt=# INSERT INTO vu_tbl_test (id, s_desc) VALUES('2', 'View insert test');
> INSERT 0 1
> tt=#
>
> regards, tom lane
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message mlane 2003-03-04 14:54:27 7.3 pg_atoi action
Previous Message dinu paul 2003-03-04 06:34:11 Installtion error