From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | mgould(at)allcoast(dot)net |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: SERIAL and Primary Key |
Date: | 2008-03-01 01:29:03 |
Message-ID: | dcc563d10802291729t202b5d82s8ef32950e46e3b60@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Feb 29, 2008 at 2:28 PM, Mike Gould <mgould(at)allcoast(dot)net> wrote:
>
>
> CREATE TABLE "fav5"."batchnumber" (
> "batchnumberid" SERIAL NOT NULL,
> "processtype" SMALLINT NOT NULL,
> "termloc" CHAR(3) NOT NULL,
> "batchno" INTEGER NOT NULL
> ) WITHOUT OIDS;
>
> With the above table definition, is batchnumberid by default also defined as
> the primary key or do I still need to define a separate Primary Key
> constraint?
Once upon a time a serial type was assumed to be a PK (or was that
unique not null???) automagically. However, this was considered bad
form since some uses of sequence did not need those extra settings.
Serial is JUST serial nowadays, and has been for quite some time.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-03-01 02:04:17 | Re: Confused about CASE |
Previous Message | brian | 2008-03-01 00:44:37 | Re: pgsql structure export to XML |