Datatype SERIAL incorrectly interpreted - Mailing list pgsql-bugs

From pgsql-bugs@postgresql.org
Subject Datatype SERIAL incorrectly interpreted
Date
Msg-id 200103281637.f2SGbq236999@hub.org
Whole thread Raw
Responses Re: Datatype SERIAL incorrectly interpreted  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Hubert Hafner (dogart@iname.com) reports a bug with a severity of 3
The lower the number the more severe it is.

Short Description
Datatype SERIAL incorrectly interpreted

Long Description
If you create a table with more than 1 SERIAL, only for the last a sequence is created by PostgreSQL. The other fields
onlyset to INTEGER, but there is no sequence for. 

Sample Code
CREATE TABLE Example (Field1 SERIAL, Field2 SERIAL);

PostgreSQL would generate:
Table Example:
Field1 as INTEGER NOT NULL DEFAULT nextval(Field1_Example_seq)
Field2 as INTEGER NOT NULL DEFAULT nextval(Field2_Example_seq)

But only Field2_Example_seq really exits!




No file was uploaded with this report

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: 7.0.3 max function
Next
From: Tom Lane
Date:
Subject: Re: Datatype SERIAL incorrectly interpreted