| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | Steve Howe <howe(at)carcass(dot)dhs(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Proposal: Solving the "Return proper effected tuple count |
| Date: | 2002-09-09 03:36:38 |
| Message-ID: | 200209090336.g893acN24720@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Howe | 2002-09-09 03:37:39 | Re: Proposal: Solving the "Return proper effected tuple count |
| Previous Message | Bruce Momjian | 2002-09-09 03:33:49 | Re: Proposal: Solving the "Return proper effected tuple |