Received: from smtp-out1.bellatlantic.net (smtp-out1.bellatlantic.net [199.45.39.156]) by hub.org (8.9.1/8.9.1) with ESMTP id LAA21872 for ; Fri, 1 Jan 1999 11:56:50 -0500 (EST) (envelope-from daybee@bellatlantic.net) Received: from daveh (client196-126-12.bellatlantic.net [151.196.126.12]) by smtp-out1.bellatlantic.net (8.9.1/8.9.1) with SMTP id LAA26380; Fri, 1 Jan 1999 11:56:47 -0500 (EST) Message-ID: <000c01be35a7$b5c74aa0$0c7ec497@daveh> From: "David Hartwig" To: "Thomas G. Lockhart" Cc: "'pgsql-interfaces@postgresql.org'" Subject: Re: [INTERFACES] ODBC CREATE TABLE failures Date: Fri, 1 Jan 1999 11:56:41 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.0810.800 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800 ----- Original Message ----- From: Thomas G. Lockhart To: David Hartwig Cc: Michael J. Sheldon ; 'pgsql-interfaces@postgresql.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