Oracle has triggers on views, so it uses per default a stored procedure, id does not need the trick with cr_dummy in the generated postgres rule; oracle cannot have this issue with duplicates. The proposed version is closer to the oracle version.
I am not sure, how Oracle deals with updates on foreign keys, but i would expect, it does not have this problem as well. It is likely, that in times before MVCC, postgres did not have these issues either.
Both problems are postgres related. Oracle might have problems on its own, but not these. So far, with this patch, i have not seem both of the problems any more.
