From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
---|---|
To: | Lauren Matheson <lmatheson(at)ivcf(dot)ca> |
Cc: | <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: changing an update via rules |
Date: | 2003-07-20 06:15:01 |
Message-ID: | 20030719231214.Y55138-100000@megazone.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On 15 Jul 2003, Lauren Matheson wrote:
> Hello,
>
> I am having difficulty setting an on update rule which seems to be
> caught in a recursive loop.
>
> Context is a table with three columns assigning users to groups with the
> third column being boolean to flag the primary group. I would like to
> set an update rule to enforce one primary group. Any suggestions on how
> to do this, or exactly how the code is getting trapped? My code is
Rules are like macro rewrites and the WHERE clauses will not help to break
the recursive loop. I think you may need to either use a trigger or
something like a view so that the actual action happens on a different
table.
From | Date | Subject | |
---|---|---|---|
Next Message | Matthew Horoschun | 2003-07-20 06:19:07 | Re: SECURITY DEFINER changes CURRENT_USER? |
Previous Message | Stephan Szabo | 2003-07-20 06:11:34 | Re: min() and NaN |