| From: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | David Hartwig <daybee(at)bellatlantic(dot)net> |
| Cc: | "Michael J(dot) Sheldon" <msheldon(at)cbrcomm(dot)com>, "'pgsql-interfaces(at)postgresql(dot)org'" <pgsql-interfaces(at)postgreSQL(dot)org> |
| Subject: | Re: [INTERFACES] ODBC CREATE TABLE failures |
| Date: | 1999-01-01 14:36:33 |
| Message-ID: | 368CDD71.D9238630@alumni.caltech.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
> The PostgreSQL backend does
> not currently support the foreign keys syntax nor the UNIQUE keyword.
> However, they can be implemented using other methods.
> For unique, create a unique index on the necessary fields.
NOTICE: CREATE TABLE/UNIQUE will create implicit index
check_directory for table fmgroups
The UNIQUE keyword is supported, unless there is some other feature or
behavior that you are expecting?
And, to split hairs, Postgres does support the foreign key *syntax*, but
throws it away and does nothing with it in the backend. So, I'd say it
supports foreign key syntax but does not support foreign keys ;)
Regards.
- Tom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Eberhard Scholz | 1999-01-01 16:02:39 | Installing pgaccess |
| Previous Message | David Hartwig | 1999-01-01 06:10:41 | Re: [INTERFACES] ODBC CREATE TABLE failures |