Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: BUG #2102: Backend reports wrong number of affected rows for a
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: bfraci(at)aol(dot)com
- Cc: pgsql-bugs(at)postgresql(dot)org
- Subject: Re: BUG #2102: Backend reports wrong number of affected rows for a
- Date: Tue, 27 Dec 2005 10:20:52 -0500
- Message-id: <23045.1135696852@sss.pgh.pa.us> <text/plain>
bfraci(at)aol(dot)com writes: > In my case we have an unconditional instead rule. The original query was an update and the instead rule replaced it with an update of another table; an update was replaced with an update. Then I should expect to see the status of the last query that was inserted by the instead rule. So I should not see a status of zero. Well, you'll see the status of the last UPDATE executed due to a rule ... but that doesn't mean it couldn't have updated zero rows. It might be worth pointing out here that conditional rules insert queries that have the condition added to their WHERE clause; if the condition is false then no rows are going to get processed. regards, tom lane
- References:
- Prev by Date: Re: BUG #2123: join between stored procedures
- Next by Date: Re: BUG #2127: Regular Expression Limits Do Not Work
- Previous by thread: Re: BUG #2102: Backend reports wrong number of affected rows for a
- Next by thread: pgsql8.1: About COPY Command and system clomn oid
- Indexes: