Re: Proposal: Solving the "Return proper effected tuple count
От | Bruce Momjian |
---|---|
Тема | Re: Proposal: Solving the "Return proper effected tuple count |
Дата | |
Msg-id | 200209090336.g893acN24720@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: Proposal: Solving the "Return proper effected tuple (Joe Conway <mail@joeconway.com>) |
Ответы |
Re: Proposal: Solving the "Return proper effected tuple count
|
Список | pgsql-hackers |
Joe Conway wrote: > Sure, but that's why I am in favor of changing the tag. If you did: > > DELETE FROM fooview WHERE name LIKE 'Joe%'; > > and got: > > MUTATED 507324 3 > > it would mean that 3 tuples in total were affected by all of the > substitute operations, only of of them being an INSERT, and the Oid of > the lone INSERT was 507324. If instead I got: > > DELETE 0 > > I'd be back to having no useful information. Did any rows in fooview > match the criteria "LIKE 'Joe%'"? Did any data in my database get > altered? Can't tell from this. OK. Do any people have INSTEAD rules where there are not commands matching the original query tag? Can anyone think of such a case being created? The only one I can think of is UPDATE implemented as separate INSERT and DELETE commands. -- 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 по дате отправления: