On Sat, Sep 26, 2009 at 12:35 PM, Tom Lane <[email protected]> wrote: > "Stefan" <[email protected]> writes: >> The problem is that if it is no record in the table, it seems that first the >> INSERT command is issued and after that the UPDATE command is issued, too. > > Well, yeah. That's exactly how it's documented to work: an ON INSERT > rule is executed after the INSERT proper.
I'm confused. DO INSTEAD doesn't mean DO INSTEAD? > You could maybe make this work with a BEFORE INSERT trigger. I'm not sure you can make it reliable though. ...Robert -- Sent via pgsql-bugs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
