| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Grzegorz Jaskiewicz <gj(at)pointblue(dot)com(dot)pl>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: affected rows count |
| Date: | 2008-12-22 20:16:56 |
| Message-ID: | 1229977016.5854.17.camel@dell.linuxdev.us.dell.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2008-12-22 20:18:57 | Re: [PATCHES] Infrastructure changes for recovery (v8) |
| Previous Message | Bruce Momjian | 2008-12-22 20:07:52 | Re: affected rows count |