How to handle a requirement for nextval - Mailing list pgsql-sql

From The Web Administrator
Subject How to handle a requirement for nextval
Date
Msg-id 35609B0F.52A63C2@wizard.ca
Whole thread Raw
Responses Re: [SQL] How to handle a requirement for nextval  (Herouth Maoz <herouth@oumail.openu.ac.il>)
Re: [SQL] How to handle a requirement for nextval  ("Jose' Soares Da Silva" <sferac@bo.nettuno.it>)
List pgsql-sql
I am still struggling on a few issues, have got my first little database
up and running, and am quite happy with PostGres, but I cannot figure
out how to create a table which can have a field that autoincrements..
I am sure that somewhere in the oid terminology it is built in, but I
want to have a counter on some table entries..  ie...
CREATE TABLE clothing_type (
      type_id INT NOT NULL,
      description TEXT,
      for_sex CHAR
);
INSERT INTO clothing_type (
   description,
   for_sex
) VALUES (
   'pants',
   'm'
);

What I want is that the Primary Key (Only Key) be type_id, and int, and
the first item that I insert should have type_id as '1', next will be
'2'  etc..
I could have every insert into this table include a type_id, but that
seems unessary.
Can I have something like default='nextval' ?


pgsql-sql by date:

Previous
From: Natalino Picone
Date:
Subject: Postgres Database Grows
Next
From: coronach@datacruz.com (Mike Lemler)
Date:
Subject: Case in-sensitive searches