Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f2EI9Kx56017 for ; Wed, 14 Mar 2001 13:09:20 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f2EI9It28314; Wed, 14 Mar 2001 13:09:18 -0500 (EST) To: Tim Perdue cc: pgsql-sql@postgresql.org Subject: Re: Rule/currval() issue In-reply-to: <20010314115015.R670@mail.perdue.net> References: <20010314115015.R670@mail.perdue.net> Comments: In-reply-to Tim Perdue message dated "Wed, 14 Mar 2001 11:50:15 -0600" Date: Wed, 14 Mar 2001 13:09:18 -0500 Message-ID: <28311.984593358@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200103/286 X-Sequence-Number: 1948 Tim Perdue writes: > This is related to the plpgsql project I was working on this morning. I'm > trying to create a rule, so that when a row is inserted into a certain table, > we also create a row over in a "counter table". The problem lies in getting > the primary key value (from the sequence) so it can be inserted in that > related table. You probably should be using a trigger, not a rule at all. regards, tom lane