Hi, here we go again...
As you know there is a problem executing something like:
create table foo (
create view v_foo as select * from foo;
create rule ins_rule as on insert to v_foo do instead
insert into foo(col1, col2) values (new.col1, new.col2);
insert into v_foo(col2) values (1);
this give an error like:
psql:f:/views.sql:13: ERROR: null value in column "col1" violates
There is a workaround about this creating default values to the view.
Now, for updateable views we need this happen automatically, attached
there is a solution to this.
The only problem i have found until now is that
update v_foo set col1 = DEFAULT; execute nextval twice per every record.
so there will be a gasp between numbers, but AFAIK nextval has no guarantee
of returning sequential numbers.
Any comments on this?
(DBA: DataBase Aniquilator ;)
pgsql-hackers by date
|Next:||From: Jochem van Dieten||Date: 2005-05-28 13:30:46|
|Subject: Re: overlaps() does not work as expected?|
|Previous:||From: Tom Lane||Date: 2005-05-28 05:11:20|
|Subject: Re: INOUT/OUT problems with IMMUTABLE |