On Mon, 2008-12-22 at 15:07 -0500, Bruce Momjian wrote: > Grzegorz Jaskiewicz wrote: > > Hey folks, > > > > It doesn't stop to bug me, that postgres will return 0 number of > > affected rows, if table is triggered. > > Now, question is - is this fixable, but no one cares, or is it some > > sort of a design/implementation flaw and we just have to live with it. > > Would you show us an example of your problem? >
This may not be the problem he's talking about, but it's bothered me for a while that there is no way to control the value returned for the affected rows. For instance, if you have an updatable view that uses a function that updates a table in a remote database, it would be nice to be able to pass that value back to the client. Regards, Jeff Davis -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers