Re: Proposal: Solving the "Return proper effected tuple count from complex commands [return]" issue
От | Steve Howe |
---|---|
Тема | Re: Proposal: Solving the "Return proper effected tuple count from complex commands [return]" issue |
Дата | |
Msg-id | 7185120386.20020909003226@carcass.dhs.org обсуждение исходный текст |
Ответ на | Re: Proposal: Solving the "Return proper effected tuple (Bruce Momjian <pgman@candle.pha.pa.us>) |
Ответы |
Re: Proposal: Solving the "Return proper effected tuple
|
Список | 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@carcass.dhs.org
В списке pgsql-hackers по дате отправления: