From: | Steve Howe <howe(at)carcass(dot)dhs(dot)org> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Joe Conway <mail(at)joeconway(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Proposal: Solving the "Return proper effected tuple count |
Date: | 2002-09-09 03:46:56 |
Message-ID: | 7385990307.20020909004656@carcass.dhs.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello Bruce,
Monday, September 9, 2002, 12:39:20 AM, you wrote:
>> BM> I don't understand this objection.
>> I misunderstood Joe's statement into thinking we wanted to sum the
>> OIDs for all INSERT commands applied :)
>> Please ignore this.
>> But now that I read it again, I would prefer having at least one OID
>> for the last inserted row. With this info, I would be able to refresh
>> my client dataset to reflect the new inserted rows.
>>
>> I see returning 0 if multiple INSERT commands issued is as weird as
>> returning some OID if multiple INSERT commands issued. But the second
>> options is usable, while the first one is useless... So I would prefer
>> retrieving the last inserted OID.
BM> We would return 0 for oid and an insert count, just like INSERT INTO ...
BM> SELECT. How is that weird?
It's not weird, or as weird as the other proposal which is retrieving
the last inserted OID number. If we can return some information for
the client, why not doing it ? :-)
-------------
Best regards,
Steve Howe mailto:howe(at)carcass(dot)dhs(dot)org
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-09-09 03:52:46 | Re: Proposal: Solving the "Return proper effected tuple count |
Previous Message | Steve Howe | 2002-09-09 03:44:37 | Re: Proposal: Solving the "Return proper effected tuple count |