Received: from olympus.scw.org (209-9-156-98.sdsl.cais.net [209.9.156.98]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eB1Kr1F20719; Fri, 1 Dec 2000 15:53:01 -0500 (EST) (envelope-from jburton@scw.org) Received: from hades (eos.scw.org [209.9.156.112]) by olympus.scw.org (8.10.1/8.10.1) with ESMTP id eB1KqWg27355; Fri, 1 Dec 2000 15:52:32 -0500 From: "Joel Burton" Organization: Support Center of Washington To: Michael Fork Date: Fri, 1 Dec 2000 15:52:31 -0500 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: RFC: User reviews of PostgreSQL RI functionality CC: pgsql-general@postgresql.org, pgsql-interfaces@postgresql.org Message-ID: <3A27C93F.1945.3EC91F@localhost> References: <3A27BFDA.8448.1A13BF@localhost> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12c) X-Archive-Number: 200012/37 X-Sequence-Number: 1217 > I was wondering if you could tell me where to get the CVS version of > the ODBC driver -- I have almost implemented foreign key support > (SQLForeignKeys), but I did it on the ODBC source available on the > postgres server. I browsed the postgres CVS repository via the web, > but couldn't find anything relevant.... It's *possible* that if you're programming directly to the ODBC API that you've always seen the RI stuff. I do my work in VBA apps (like Access), and I know that they don't see the RI errors. You can find the ODBC source in the pgsql source, at src/interfaces/odbc (or something *very* close, no source in front of me right now, sorry). If you don't want to grab the whole file just for ODBC stuff, you can use CVS to just get the contents of the src/interfaces/odbc directory. The directions say you need to use VisualC++ to compile this. Via ftp, that's in the /dev directory. -- Joel Burton, Director of Information Systems -*- jburton@scw.org Support Center of Washington (www.scw.org)