Problems in create table ?? 6.3.2

From: Dev_Al <Dev_Al/houston_rd(at)peach(dot)bmc(dot)com>
To: pgsql-general(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Problems in create table ?? 6.3.2
Date: 1998-09-04 22:33:43
Message-ID: 35F06AC7.13CD3387@peach.bmc.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Hello:
I am getting the following errors. I am using 6.3.2 on linux Redhat 5.1

create table person (person_id int not null,
marital_status char(1),
unique(person_id));
NOTICE: CREATE TABLE/UNIQUE will create implicit index
person_person_id_key for table person
CREATE
My comments: This notice looks ok.

create table longtablename (DATE_TIME_STAMP datetime not null,
UNIQUE (DATE_TIME_STAMP));
ERROR: parser: unable to construct implicit index for table
longtablename; name too long
My comments: Here if the table name is long and the column name is long
Postgres has trouble with
the index name being too long.

ALTER TABLE longtablename ADD FOREIGN KEY (person_ID) REFERENCES
person(person_id);
NOTICE: CREATE TABLE/FOREIGN KEY clause ignored; not yet implemented
ERROR: ALTER TABLE/ADD CONSTRAINT not yet implemented
My comments: Here, since the table is empty, should this not be easy for
the postgres to alter the table??

ALTER TABLE person ADD
check (marital_status in ("T","F"))
;
ERROR: parser: parse error at or near "in"
EOF
My comments: Here, since the table is empty, should this not be easy for
the postgres to alter the table??

Browse pgsql-general by date

  From Date Subject
Next Message Erik Norvelle 1998-09-05 17:52:14 Re: pgsql-general-digest V1 #60
Previous Message Chris Hardie 1998-09-04 21:58:36 DBI w/Postgres

Browse pgsql-hackers by date

  From Date Subject
Next Message Roland Roberts 1998-09-05 00:33:12 MIN not defined for OID types
Previous Message Brook Milligan 1998-09-04 21:53:26 Re: [HACKERS] Open portability issues