Re: "strange" rule behavior with nextval on new.* fields - Mailing list pgsql-bugs

From Fabien COELHO
Subject Re: "strange" rule behavior with nextval on new.* fields
Date
Msg-id Pine.LNX.4.61.0411120828230.23462@sablons.cri.ensmp.fr
Whole thread Raw
In response to "strange" rule behavior with nextval on new.* fields  (Fabien COELHO <coelho@cri.ensmp.fr>)
List pgsql-bugs
> I'd like to report the following "strange" behavior that I encountered
> while trying (a bad idea, I know) to use a rule as a "poor man sql-trigger".

I noticed that I forget about the bug report guidelines...

The above mentionned strange behavior is with a recent cvs tree, between
beta3 and beta4, on a debian linux box under an intel architecture.

--
Fabien Coelho - coelho@cri.ensmp.fr

pgsql-bugs by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: BUG #1315: unconvertible BIG5 character 0xf9d8
Next
From: Michael Fuhr
Date:
Subject: Re: "strange" rule behavior with nextval on new.* fields