> Is this behavior intended in the backend? The problem is that when
you
> create a rule on an object that calls a stored function and invoke
that
> rule on an insert/update/delete statement your insert/update/delete
> statement will now return a query result to the front end over the
FE/BE
> protocol.
Since this behavior is essential to the rule system, imho the actual
source
of problems is, that PostgreSQL does not have "real stored procedures"
==
functions that do not have a return value or set (C lingo: void
func_a(x)).
The usual view rule that needs enhanced processing intelligence would
then call a stored procedure and not a function.
The easy way out would be to write rules with instead actions, that
call insert/update/delete statemants directly. This often works
for the more common cases.
Andreas
