From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | mito <milos(dot)orszag(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Affected rows count by rule as condtition |
Date: | 2009-04-13 16:35:13 |
Message-ID: | 603c8f070904130935p1cf24675o29dea948beb2329@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Apr 13, 2009 at 12:12 PM, mito <milos(dot)orszag(at)gmail(dot)com> wrote:
> Hi,
> is there any way how to count affected rows by on update rule and use it as
> part of condtions.
>
> Example:
>
>
> CREATE OR REPLACE RULE "_UPDATE" AS ON UPDATE TO "users" DO INSTEAD (
> UPDATE "s_users" SET
> id = new.id,
> login = new.login,
> WHERE id IN (SELECT id FROM "s_users" ) AND 2 > (SELECT count(new.id)) ;
>
> Error: agregate functions not allowed in WHERE statement
>
> It need to simulate unique constraint on field s_users.new_id, so it should
> deny to update multiple rows with same value.
>
> Any suggestions are welcome.
Well, you could probably make this compile by rewriting the broken
part as "SELECT SUM(1) FROM s_users WHERE id = NEW.id", but it won't
guarantee uniqueness in the face of concurrent transactions, even if
you use SERIALIZABLE mode.
There's a reason that unique constraints are built into the
database.... you should use them.
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2009-04-13 16:46:23 | Re: New trigger option of pg_standby |
Previous Message | Jaime Casanova | 2009-04-13 16:27:20 | Re: Affected rows count by rule as condtition |