Received: from golem.jpl.nasa.gov (dialin-112.jpl.nasa.gov [128.149.231.112])
	by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eAH6aps17468
	for <pgsql-interfaces@postgresql.org>;
	Fri, 17 Nov 2000 01:36:51 -0500 (EST)
	(envelope-from lockhart@alumni.caltech.edu)
Received: from alumni.caltech.edu (localhost.localdomain [127.0.0.1])
	by golem.jpl.nasa.gov (Postfix) with ESMTP
	id CC1C517C5E; Fri, 17 Nov 2000 06:53:17 +0000 (UTC)
Message-ID: <3A14D5DD.56D36A3F@alumni.caltech.edu>
Date: Fri, 17 Nov 2000 06:53:17 +0000
From: Thomas Lockhart <lockhart@alumni.caltech.edu>
Organization: Yes
X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.15-4mdksmp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Kevin Lo <kevin.lo@toptk.com>
Cc: Robert Smith <rsmith@crepsunited.com>, pgsql-interfaces@postgresql.org
Subject: Re: ODBC Maintainer?
References: <Pine.BSF.4.21.0011151449410.35209-100000@iclub.nsu.ru>
	<002901c04f19$486550f0$2101a8c6@CREPSUNITED.COM>
	<3A14AE3B.191E1C79@alumni.caltech.edu> <3A14C6AC.9070109@toptk.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Archive-Number: 200011/194
X-Sequence-Number: 230

> I'll be a volunteer to implement odbc driver. Just wondering why don't
> import unixODBC code into Postgres src?

That is possible, I suppose. 

My (admittedly vague) recollection is that the unixODBC folks took the
psqlODBC code from our tree and modified it. They may have contributed
back some patches, but afaik they forked the code and had no interest in
keeping the code base consistant :(

If the unixODBC code is a superset of what we have (or could be made so)
then perhaps it would be a better choice to work from. But we should
make sure that our last year's improvements don't get lost.

                     - Thomas