Re: sorry, now with subject... trigger & nextval(seq) - Mailing list pgsql-sql

From Adrian Klaver
Subject Re: sorry, now with subject... trigger & nextval(seq)
Date
Msg-id 201005201846.53125.adrian.klaver@gmail.com
Whole thread Raw
In response to sorry, now with subject... trigger & nextval(seq)  (tlange@gwdg.de)
Responses Re: sorry, now with subject... trigger & nextval(seq)  (Daniel Migowski <dmigowski@ikoffice.de>)
List pgsql-sql
On Thursday 20 May 2010 5:53:51 pm tlange@gwdg.de wrote:
> Hello all,
>
> I'm new to triggers in PostgreSQL. I have to create a trigger on insert to
> increment a sequence to overcome MS-Access' limitation in acknowledging
> serial "datatype".
>
> Could anyone put me on right track? I was looking the whole day for
> references on that... Years ago I quickly found a reference how to do it
> in Oracle. However, I could not find anything that explained how to do
> this in postgresql... I think, it should go the direction see below... But
> how exactly :-/ ?
>
>
> Many thanks for any help, Torsten
>
>
> create table testtab (
>   pid bigint,
>   sometext text
> );
>
> create sequence test;
>
> -- hmm something like this...?
> CREATE FUNCTION count_up (varchar) RETURNS opaque AS '
>   DECLARE
>     pid_num bigint;
>   BEGIN
>     select into pid_num from select nextval($);
>     RETURN pid_num;
>   END;
> ' LANGUAGE 'plpgsql';
>
> -- and how will the trigger looks like
> ???

You know serial is just a shortcut for:

pid int NOT NULL DEFAULT nextval('seq')

I think you will find Access will place nice if you use the long form to define 
your autoincrement.



-- 
Adrian Klaver
adrian.klaver@gmail.com


pgsql-sql by date:

Previous
From: tlange@gwdg.de
Date:
Subject: sorry, now with subject... trigger & nextval(seq)
Next
From: Richard Broersma
Date:
Subject: Re: