Very little interest exists in working on user-specified rules. They are practically deprecated.
Ah - pity - see my last comment to Adrian's
Any interest in perhaps providing a choice via a configuration parameter?
If anything is done it would have to be new syntax.
A much bigger task surely.
2) Use INSTEAD OF triggers:
Unfortunately the same functionality as in my example with the RULE is not supported for triggers on views : from the manual
INSTEAD OF triggers may only be
defined on views, and only at row level;
A RULE is essentially a statement-level operation which is what I need for this particular case. A row-level trigger would not work because it cannot "see" the query causing it to be fired, and also , (most importantly) is not fired at all if no rows match the original query, whereas a RULE is always in effect regardless of which rows are involved. before. I should add that the RULE I showed in my example is not the only RULE being used on this view - there are other conditional RULEs, and the combined effect is of being able to change the effect of the original statement into a set of new statements, one of which does what is needed.
And if you are now inclined to say "well, maybe the
application itself is poorly written and should be changed" - I
would have to agree, but that is not mine to change.
But I suppose that my next question, given what you both say about the RULE system being a dead-end, is whether there is any likelihood of supporting an INSTEAD OF trigger on a view at statement level? Maybe that stands more chance of going somewhere?
Cheers, John Lumby
