Received: from golem.jpl.nasa.gov (IDENT:root@hectic-2.jpl.nasa.gov [128.149.68.204]) by hub.org (8.9.1/8.9.1) with ESMTP id JAA12141 for ; Fri, 1 Jan 1999 09:39:54 -0500 (EST) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (localhost [127.0.0.1]) by golem.jpl.nasa.gov (8.8.5/8.8.5) with ESMTP id OAA10771; Fri, 1 Jan 1999 14:36:33 GMT Sender: tgl@mythos.jpl.nasa.gov Message-ID: <368CDD71.D9238630@alumni.caltech.edu> Date: Fri, 01 Jan 1999 14:36:33 +0000 From: "Thomas G. Lockhart" Organization: Caltech/JPL X-Mailer: Mozilla 4.07 [en] (X11; I; Linux 2.0.30 i686) MIME-Version: 1.0 To: David Hartwig CC: "Michael J. Sheldon" , "'pgsql-interfaces@postgresql.org'" Subject: Re: [INTERFACES] ODBC CREATE TABLE failures References: <01d601be354d$77b72dc0$637dc497@daveh> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > 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