Thread
-
Serial Data Type Failure
David Hartwig <daveh@insightdist.com> — 1998-09-18T17:55:25Z
Tom, The following came from the most recient snapshot. I know your away for a few days. I will give it a look-see if I get time this weekend CREATE TABLE foo ( id serial primary key, name varchar(32) ); NOTICE: CREATE TABLE will create implicit sequence foo_id_seq for SERIAL column foo.id NOTICE: CREATE TABLE/PRIMARY KEY will create implicit index foo_pkey for table foo CREATE -- This is good. Thanks. CREATE TABLE bar ( id serial, name varchar(32) ); NOTICE: CREATE TABLE will create implicit sequence bar_id_key for SERIAL column bar.id NOTICE: CREATE TABLE/UNIQUE will create implicit index bar_id_key for table bar ERROR: Cannot create index: 'bar_id_key' already exists -- This is bad. Sorry. -
Re: Serial Data Type Failure
Thomas Lockhart <lockhart@alumni.caltech.edu> — 1998-09-21T00:50:13Z
> The following came from the most recient snapshot. > CREATE TABLE bar ( > id serial, > name varchar(32) > ); > NOTICE: CREATE TABLE will create implicit sequence bar_id_key for > SERIAL column bar.id > NOTICE: CREATE TABLE/UNIQUE will create implicit index bar_id_key for > table bar > ERROR: Cannot create index: 'bar_id_key' already exists > -- This is bad. Sorry. OK, will look at it if you haven't fixed it already... - Tom -
Re: [HACKERS] Re: Serial Data Type Failure
Thomas Lockhart <lockhart@alumni.caltech.edu> — 1998-09-21T05:41:25Z
> > ERROR: Cannot create index: 'bar_id_key' already exists > > -- This is bad. Sorry. postgres=> CREATE TABLE bar ( postgres-> id serial, postgres-> name varchar(32) postgres-> ); NOTICE: CREATE TABLE will create implicit sequence bar_id_seq for SERIAL column bar.id NOTICE: CREATE TABLE/UNIQUE will create implicit index bar_id_key for table bar CREATE I hadn't noticed that there was a positional dependency in the code I had moved around to implement the SERIAL PRIMARY KEY feature. Sorry about that. Patch enclosed. Will commit to source tree soon... - Tom