From: | "David Hartwig" <daybee(at)bellatlantic(dot)net> |
---|---|
To: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
Cc: | "'pgsql-interfaces(at)postgresql(dot)org'" <pgsql-interfaces(at)postgreSQL(dot)org> |
Subject: | Re: [INTERFACES] ODBC CREATE TABLE failures |
Date: | 1999-01-01 16:56:41 |
Message-ID: | 000c01be35a7$b5c74aa0$0c7ec497@daveh |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
----- Original Message -----
From: Thomas G. Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>
To: David Hartwig <daybee(at)bellatlantic(dot)net>
Cc: Michael J. Sheldon <msheldon(at)cbrcomm(dot)com>;
'pgsql-interfaces(at)postgresql(dot)org' <pgsql-interfaces(at)postgreSQL(dot)org>
Sent: Friday, January 01, 1999 9:36 AM
Subject: Re: [INTERFACES] ODBC CREATE TABLE failures
>> 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 ;)
That's what I get for answering e-mail at half past 1999.
Happy New Year
From | Date | Subject | |
---|---|---|---|
Next Message | Valerio Santinelli | 1999-01-02 00:11:30 | MSAccess and Searches |
Previous Message | Eberhard Scholz | 1999-01-01 16:02:39 | Installing pgaccess |