| From: | Grzegorz Jaskiewicz <gj(at)pointblue(dot)com(dot)pl> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: affected rows count |
| Date: | 2008-12-22 21:28:14 |
| Message-ID: | 4B57653C-546F-4FFD-B542-42D38F2861A8@pointblue.com.pl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2008-12-22, at 21:07, 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?
Dunno what's wrong with me lately. I was under impression, that about
1/2 year ago on 8.1 I wasn't able to get row count anymore if there
was a trigger on a table. Well, affected row count would be always 0
than.
But trying now on cvs head, it all works great. heh, I am terribly
sorry...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dawid Kuroczko | 2008-12-22 21:35:31 | Re: affected rows count |
| Previous Message | Andrew Dunstan | 2008-12-22 21:22:14 | HAVE_FSEEKO for WIN32 |