Re: affected rows count

From: Grzegorz Jaskiewicz <gj(at)pointblue(dot)com(dot)pl>
To: "Dawid Kuroczko" <qnex42(at)gmail(dot)com>
Cc: "Bruce Momjian" <bruce(at)momjian(dot)us>, "PostgreSQL-development Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: affected rows count
Date: 2008-12-22 21:38:37
Message-ID: 83BCFEB1-2941-4A28-9063-A81544DD33B6@pointblue.com.pl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 2008-12-22, at 22:35, Dawid Kuroczko wrote:
>
>
> atlantis=> CREATE OR REPLACE FUNCTION foo_trigger() RETURNS trigger AS
> $$ BEGIN UPDATE bar SET t=NEW.t WHERE i=NEW.i; RETURN NULL; END; $$
> LANGUAGE plpgsql;
> atlantis=> CREATE TRIGGER foo_update BEFORE UPDATE ON foo FOR EACH ROW
> EXECUTE PROCEDURE foo_trigger();
> CREATE TRIGGER
> CREATE FUNCTION
> atlantis=> UPDATE foo SET t='##'||t;
> UPDATE 0
> ^^^^^^^^^^
>
> Grzegorz means such a situation. Personally I understand the current
> behavior to be correct -- since no row in that table is updated.

that's not quite what I meant. It is correct behavior in this
situation - since we didn't update anything.
Like I said, it is my bad - I should have tested it before emailing -
hackers... So far my ratio of useful emails here is very low. :/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2008-12-22 22:36:42 Re: HAVE_FSEEKO for WIN32
Previous Message Dawid Kuroczko 2008-12-22 21:35:31 Re: affected rows count