Message-Id: <3538D990.12E4A45D@insightdist.com>
Date: Sat, 18 Apr 1998 12:49:20 -0400
From: Byron Nikolaidis <byronn@insightdist.com>
Mime-Version: 1.0
To: "pgsql-interfaces@postgreSQL.org" <pgsql-interfaces@postgreSQL.org>,
	The Hermit Hacker <scrappy@hub.org>, "Julia A.Case" <julie@postgreSQL.org>,
	Vince Vielhaber <vev@michvhf.com>,
	Scott Tomer x6214 Austin <stomer@bmc.com>,
	Gerhard Reithofer <gerhardr@tech-edv.co.at>
Subject: ODBC 16 bit support
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello all,

Boy the discussions on this list are certainly lively these days!

I didn't say that "Postgres" shouldn't offer a 16 bit ODBC driver to go
with its distribution. After all, you still have the old PostODBC driver
that works for 16 bit.  I said that this new driver probably shouldn't
support 16 bit.  It is still, as it always has been, YOUR decision to
use this new driver or not. We (meaning Insight) needed a good solid
driver for our clients and the old one just wasn't cutting it, thus a
rewrite, reorganization, whatever you want to call it, was necessary for
us.  We offered this driver in the hopes of helping the Postgres effort.
When we made this new driver available, we provided a whole list of
things that were changed or removed or enhanced to make this driver work
really well.  The first thing on the removed list is "Win 3.1".  How
come now everybody is complaining?  Didn't you read the list?

Now that said, on my own time over the weekend, I will look into what it
would take to make the current driver support win3.1.  But if it turns
out that it would degrade the performance of the driver for 32bit or
require major rework, I would probably have to say, it would be best to
have 2 separate drivers.

Regards,

Byron