X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 8E6E3329E73 for ; Wed, 22 Sep 2004 16:30:03 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 15250-08 for ; Wed, 22 Sep 2004 15:29:56 +0000 (GMT) Received: from laptop.kieser.net (unknown [195.166.116.245]) by svr1.postgresql.org (Postfix) with ESMTP id CEFFA329E70 for ; Wed, 22 Sep 2004 16:29:54 +0100 (BST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by laptop.kieser.net (Postfix) with ESMTP id CA38919480; Wed, 22 Sep 2004 16:30:06 +0100 (BST) Message-ID: <41519A7E.8050803@kieser.net> Date: Wed, 22 Sep 2004 16:30:06 +0100 From: Bradley Kieser User-Agent: Mozilla Thunderbird 0.8 (X11/20040913) X-Accept-Language: en, en-us MIME-Version: 1.0 To: Michael Fuhr Cc: pgsql-admin@postgresql.org Subject: Re: Getting the OID of inserted row in a rule References: <41517C66.9040709@kieser.net> <20040922152643.GA92429@winnie.fuhr.org> In-Reply-To: <20040922152643.GA92429@winnie.fuhr.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200409/207 X-Sequence-Number: 14910 Hi Michael, But what if another insert happens in the mean time? Then the sequence would have advanced that the data will be scrambled. |Given that this could be a very active dataset, that situation is almost certain to occur. Brad Michael Fuhr wrote: >On Wed, Sep 22, 2004 at 02:21:42PM +0100, Bradley Kieser wrote: > > >>I have a rule on a view that needs to insert into two tables. The one >>table has a serial ID as its unique key. The second table links to the >>first one in one of its columns. >> >>I would prefer to keep this as a rule-based solution and not have to >>write a function as I hope to relicate the solution across many views. >> >>I need to either be able to select nextval() the ID for the first table >>and somehow store this in the rule (but I don't see that rules support >>variables) or I need to somehow obtain the OID from the first insert in >>order to select back the ID that was assigned during the insert and pass >>it to the second insert (trivial to do as the second insert is then >>simply a select-based insert, provided that I know the OID of that first >>row!). >> >> > >The second insert should be able to use currval() to get the current >value of the sequence used in the first insert. Here's an example: > >CREATE RULE v_ins AS ON INSERT TO v DO INSTEAD ( > INSERT INTO a (xxx) VALUES (NEW.xxx); > INSERT INTO b (col1, col2, col3) VALUES (NEW.col1, NEW.col2, currval('a_id_seq')) >); > > >