Skip site navigation (1)
Skip section navigation (2)
Thanks for the additional insight. Then everything is working as it should.
Thanks for your help.
Brent
Peripheral Links
Header And Logo
|
Site Navigation
Re: BUG #2102: Backend reports wrong number of affected rows for a
- From: BFRACI(at)aol(dot)com
- To: tgl(at)sss(dot)pgh(dot)pa(dot)us
- Cc: pgsql-bugs(at)postgresql(dot)org
- Subject: Re: BUG #2102: Backend reports wrong number of affected rows for a
- Date: Sat, 31 Dec 2005 00:53:32 EST
- Message-id: <fe(dot)22a807ac(dot)30e776dc(at)aol(dot)com>
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.
Thanks for the additional insight. Then everything is working as it should.
Thanks for your help.
Brent
- Prev by Date: Re: COPY TO STDOUT BINARY
- Next by Date: Re: BUG #2136: plperl doesn't work, plperlu - yes
- Previous by thread: BUG #2137: CREATE DATABASE permission is not inherited.
- Next by thread: [no subject]
- Indexes: