Re: [ADMIN] Rules on a view overwrite default values. Any way to reinstate them?

[Tom Lane]

Bradley Kieser <[EMAIL PROTECTED]> writes:
> The problem is that rules on a view mean that the default values for NOT 
> NULL columns (used extensively) no longer trigger!

The way you're supposed to fix this is to attach default values to the
view itself.

ALTER TABLE myview ALTER COLUMN updated_time SET DEFAULT now();

Now an INSERT on myview will include the correct expression before view
expansion happens.

I'm not sure how long we've had this, but it's definitely in 7.4.

regards, tom lane

---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

[ADMIN] Rules on a view overwrite default values. Any way to reinstate them?

[Bradley Kieser]

Hi,
I use views extensively to implement security on tables. This requires 
each table to have a view. All updates, inserts and deletes take place 
through the view. The view has rules for each of these operations 
defining security for that table. Under other conditions, the view also 
removes complex views of the underlying data from the application layer 
by supplying a view where the rules for update, insert and delete 
implement business logic.

The problem is that rules on a view mean that the default values for NOT 
NULL columns (used extensively) no longer trigger!

E.g.
Table A had column "updated_time" which is not null default now().
Inserting into the view on table A where "updated_time" has not been 
supplied will not fill in "now()". It will attempt to put in a null 
value and hence the insert will fail in the insert rule on that view.

Is there any way to tell PG to implement the triggers on the underlying 
table? It will make it extremely difficult to implement this schema if I 
have to try to put in null field handling... and it really should be PG 
doing this not me! No doubt if this is a bug, it will be fixed in 8.x!

Thanks,
Brad
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
 subscribe-nomail command to [EMAIL PROTECTED] so that your
 message can get through to the mailing list cleanly