Re: Lock strategies!

From: Jeff <threshar(at)torgo(dot)978(dot)org>
To: MaRcElO PeReIrA <gandalf_mp(at)yahoo(dot)com(dot)br>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Lock strategies!
Date: 2003-11-24 14:28:26
Message-ID: 20031124092826.228bd067.threshar@torgo.978.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, 24 Nov 2003 10:20:07 -0300 (ART)
MaRcElO PeReIrA <gandalf_mp(at)yahoo(dot)com(dot)br> wrote:

> Hi guys,
>
> I have a simple table:
>
> teste=# \d forn
> Table "public.forn"
> Column | Type | Modifiers
> ---------+---------+-------------------------------------------------
> -----
> id | integer | not null default
> nextval('public.forn_id_seq'::text)
> forn_id | integer |
> descrip | text |
>

Why not make forn_id a sequence as well?
then you simply call nextval('forn_id_seq')

--
Jeff Trout <jeff(at)jefftrout(dot)com>
http://www.jefftrout.com/
http://www.stuarthamm.net/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Christian Traber 2003-11-24 14:30:44 autocommit in 7.4
Previous Message Claudio Lapidus 2003-11-24 13:44:10 Re: rounding timestamps