> Actually, I am seeing some unexpected behavior, or rather behavior that
> I wouldn't expect. After the first UPDATE in the rule, NEW and OLD are
> gone.
I guess the end-result behaviour I am looking for (as you mentioned) is having an update-able view
behave exactly as if it were a table in regard to update and delete statements. (Delete
statements had a similar behavior behaviour, but I got around that problem by using "delete
cascade" on the leaf tables.)
Regards,
Richard Broersma Jr.
