Skip site navigation (1) Skip section navigation (2)

Re: insert/update/delete statements returning a query response

From: "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at>
To: "Barry Lind" <barry(at)xythos(dot)com>, "PostgreSQL Development" <pgsql-hackers(at)postgresql(dot)org>
Cc: <stuart(at)zapata(dot)org>
Subject: Re: insert/update/delete statements returning a query response
Date: 2001-11-27 09:14:46
Message-ID: 46C15C39FEB2C44BA555E356FBCD6FA41EB435@m0114.s-mxs.net (view raw or flat)
Thread:
Lists: pgsql-hackers
> 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

pgsql-hackers by date

Next:From: Zeugswetter Andreas SB SDDate: 2001-11-27 10:04:42
Subject: Re: Pre-page images in WAL
Previous:From: Vincent.GaboriauDate: 2001-11-27 08:42:56
Subject: Re: [HACKERS] upper and lower doesn't work with german umlaut?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group