Re: "strange" rule behavior with nextval on new.* fields

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: PostgreSQL Bugs List <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: "strange" rule behavior with nextval on new.* fields
Date: 2004-11-12 07:30:34
Message-ID: Pine.LNX.4.61.0411120828230.23462@sablons.cri.ensmp.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)cri(dot)ensmp(dot)fr

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Fuhr 2004-11-12 09:03:32 Re: "strange" rule behavior with nextval on new.* fields
Previous Message Tatsuo Ishii 2004-11-12 01:16:36 Re: BUG #1315: unconvertible BIG5 character 0xf9d8