Re: Proposal: Solving the "Return proper effected tuple count from complex commands [return]" issue

From: Steve Howe <howe(at)carcass(dot)dhs(dot)org>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Proposal: Solving the "Return proper effected tuple count from complex commands [return]" issue
Date: 2002-09-09 03:32:26
Message-ID: 7185120386.20020909003226@carcass.dhs.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello Bruce,

Monday, September 9, 2002, 12:21:11 AM, you wrote:

BM> Steve Howe wrote:
>> Hello Bruce,
>>

>> But this *is* the total number of rows affected. There is no current
>> (defined) behavior of "rows affected by the same kind of command
>> issued", although I agree it makes some sense.

BM> Yes, that is a good point, i.e. rows effected. However, see my previous
BM> email on how this doesn't play with with INSERT.
I agree with your point. In fact, since everybody until now seems to
agree that the "last command" behavior isn't consistent, I think Tom's
suggestion is the best.

BM> We don't like to add complexity if we can help it.
I understand. If we can reach an agreement on another way, that's ok
for me...

We still have to hear the other developers about this, but for a
while, my votes go to Proposal's #2 (by Tom) and Proposal #3 if enough
people consider it important.

-------------
Best regards,
Steve Howe mailto:howe(at)carcass(dot)dhs(dot)org

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-09-09 03:33:49 Re: Proposal: Solving the "Return proper effected tuple
Previous Message Joe Conway 2002-09-09 03:32:14 Re: Proposal: Solving the "Return proper effected tuple