Re: Proposal: Solving the "Return proper effected tuple
От | Bruce Momjian |
---|---|
Тема | Re: Proposal: Solving the "Return proper effected tuple |
Дата | |
Msg-id | 200209090339.g893dKT25023@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: Proposal: Solving the "Return proper effected tuple count (Steve Howe <howe@carcass.dhs.org>) |
Ответы |
Re: Proposal: Solving the "Return proper effected tuple count
|
Список | pgsql-hackers |
Steve Howe wrote: > Hello Bruce, > > Monday, September 9, 2002, 12:22:26 AM, you wrote: > > BM> Steve Howe wrote: > >> JC> return OID if sum of all replacement INSERTs in the rule inserted > >> JC> only one row, else zero > >> I don't agree with this one since it would lead us to a meaningless > >> information... what would be the number retrieved ? Not an OID, nor > >> nothing. > > 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. We would return 0 for oid and an insert count, just like INSERT INTO ... SELECT. How is that weird? -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania19073
В списке pgsql-hackers по дате отправления: