"Stefan" <sb(at)drbott(dot)de> 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.
You could maybe make this work with a BEFORE INSERT trigger.
regards, tom lane
In response to
pgsql-bugs by date
|Next:||From: Tom Lane||Date: 2009-09-27 04:31:04|
|Subject: Re: BUG #5076: LEFT OUTER JOIN and WHERE madness |
|Previous:||From: Kris Jurka||Date: 2009-09-26 14:32:19|
|Subject: Re: [JDBC] BUG #5058: [jdbc] Silent failure with