Received: from trends.net (clio.trends.ca [209.47.148.2]) by hub.org (8.9.3/8.9.3) with ESMTP id AAA74562 for ; Fri, 1 Oct 1999 00:51:44 -0400 (EDT) (envelope-from lockhart@alumni.caltech.edu) Received: from localhost (root@hectic-2.jpl.nasa.gov [128.149.68.204]) by trends.net (8.8.8/8.8.8) with ESMTP id WAA04954 for ; Thu, 30 Sep 1999 22:50:47 -0400 (EDT) Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1]) by localhost (8.8.7/8.8.7) with ESMTP id CAA13173; Fri, 1 Oct 1999 02:50:05 GMT Sender: lockhart@trends.net Message-ID: <37F4215D.F5362B7E@alumni.caltech.edu> Date: Fri, 01 Oct 1999 02:50:05 +0000 From: Thomas Lockhart X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686) X-Accept-Language: en MIME-Version: 1.0 To: "Ansley, Michael" CC: "'pgsql-interfaces@postgresql.org'" Subject: Re: [INTERFACES] SSL and ODBC References: <1BF7C7482189D211B03F00805F8527F748C0E8@S-NATH-EXCH2> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > I presume that the ODBC driver uses libpq underneath (either statically or > dynamically loaded) to talk to the server. Actually, no! libpq requires a cygwin environment, and (perhaps) there was a worry about performance (though that doesn't seem to be an issue to me). So the ODBC driver is completely standalone. The downside is that it requires separate maintenance, and I'm pretty sure that there are some arcane issues which don't get fixed there when they change in libpq... - Thomas -- Thomas Lockhart lockhart@alumni.caltech.edu South Pasadena, California