> Is this behavior intended in the backend? The problem is that when
> create a rule on an object that calls a stored function and invoke
> rule on an insert/update/delete statement your insert/update/delete
> statement will now return a query result to the front end over the
Since this behavior is essential to the rule system, imho the actual
of problems is, that PostgreSQL does not have "real stored procedures"
functions that do not have a return value or set (C lingo: void
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.
pgsql-hackers by date
|Next:||From: Zeugswetter Andreas SB SD||Date: 2001-11-27 10:04:42|
|Subject: Re: Pre-page images in WAL |
|Previous:||From: Vincent.Gaboriau||Date: 2001-11-27 08:42:56|
|Subject: Re: [HACKERS] upper and lower doesn't work with german umlaut?|