From: Cédric Dufour (Cogito Ergo Soft) <cedric.dufour@cogito-ergo-soft.com>
To: Ken Corey <ken.corey@atomic-interactive.com>
To: Peter Atkins <peter.atkins@NXCD.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Returning PK of first insert for second insert use.
Date: Fri, 2 Aug 2002 14:59:44 +0200
Message-ID: <NDBBIFNBODNADCAOFDOAMEJECDAA.cedric.dufour@cogito-ergo-soft.com> (raw)
In-Reply-To: <1027969192.2354.206.camel@kenlinux.bithub.org>
You can retrieve the last inserted sequence value using:
currval('t_task_task_id_seq')
This is connection safe, so you get the the last ID inserted by YOUR
connection.
> -----Original Message-----
> From: pgsql-sql-owner@postgresql.org
> [mailto:pgsql-sql-owner@postgresql.org]On Behalf Of Ken Corey
> Sent: Monday, July 29, 2002 20:59
> To: Peter Atkins
> Cc: 'pgsql-sql@postgresql.org'
> Subject: Re: [SQL] Returning PK of first insert for second insert use.
>
>
> On Mon, 2002-07-29 at 19:32, Peter Atkins wrote:
> > I have two tables t_proj, t_task see below:
> >
> > CREATE TABLE t_proj (
> > proj_id SERIAL NOT NULL,
> > PRIMARY KEY (proj_id),
> > task_id integer(12),
> > user_id integer(6),
> > title varchar(35),
> > description varchar(80)
> > );
> >
> > CREATE TABLE t_task (
> > task_id SERIAL NOT NULL,
> > PRIMARY KEY (task_id),
> > title varchar(35),
> > description varchar(80)
> > );
> >
> > When I insert into t_task I need to return the task_id (PK) for
> that insert
> > to be used for the insert into the t_proj table.
> >
> > I tried using RESULT_OID but I have no idea how to obtain the
> true PK using
> > this opague id. Below is the procedure I tried to use.
>
> Since the primary key of the first table is a SERIAL, it's really
> defined as something like this:
>
> create table t_task (
> task_id int4 not null default nextval('t_task_task_id_seq'),
> ...
>
> Which means that you can predict what the next value will be, store that
> in a temporary var, and then insert it into both tables...
>
> CREATE OR REPLACE FUNCTION insertTask (varchar, varchar)
> RETURNS INTEGER AS '
>
> DECLARE
> -- local variables
> oid1 INTEGER;
> retval INTEGER;
> tempvar int4;
>
> BEGIN
> select into tempvar nextval(''t_task_task_id_seq'');
>
> INSERT INTO t_task (task_id, title, description)
> VALUES (tempvar,$1, $2);
>
> -- Everything has passed, return id as pk
> RETURN tempvar;
> END;
> ' LANGUAGE 'plpgsql';
>
> WARNING: this is not guaranteed to be the correct syntax, I didn't
> create the tables and the function to test it, but I do this kind of
> thing all the time in my functions.
>
> --
> Ken Corey CTO http://www.atomic-interactive.com 07720 440 731
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: cedric.dufour@cogito-ergo-soft.com, ken.corey@atomic-interactive.com, peter.atkins@NXCD.com
Subject: Re: Returning PK of first insert for second insert use.
In-Reply-To: <NDBBIFNBODNADCAOFDOAMEJECDAA.cedric.dufour@cogito-ergo-soft.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox