Re: Update view/table rule order of operations or race condition - Mailing list pgsql-general

From Tom Lane
Subject Re: Update view/table rule order of operations or race condition
Date
Msg-id 24216.1268157642@sss.pgh.pa.us
Whole thread Raw
In response to Re: Update view/table rule order of operations or race condition  (Dan Fitzpatrick <dan@eparklabs.com>)
Responses Re: Update view/table rule order of operations or race condition  (Dan Fitzpatrick <dan@eparklabs.com>)
List pgsql-general
Dan Fitzpatrick <dan@eparklabs.com> writes:
> The rule is creating a new value from the sequence a_a_id_seq for
> "new.options_id" on each UPDATE call. How do I use the variable
> new.options_id in the three update statements without incrementing the
> sequence again?

You don't.  This is one of the major disadvantages of rules: they're
macros, not functions, and as such don't have any real local variables.
You should probably look into whether you can do what you want with a
trigger instead of a rule.

            regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: question on 8.4.2 build postgres C functions
Next
From: Thomas Kellerer
Date:
Subject: Re: \copy command: how to define a tab character as the delimiter