pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Stephen Davies <scldad@sdc.com.au>
To: The Hermit Hacker <scrappy@hub.org>
Cc: pgsql-interfaces@postgreSQL.org <pgsql-interfaces@postgreSQL.org>
Subject: Re: [INTERFACES] Re: ODBC 16 bit support
Date: Sun, 19 Apr 1998 22:04:14 +0930
Message-ID: <199804191234.WAA09636@mustang.sdc.com.au> (raw)
In-Reply-To: <Pine.BSF.3.96.980418150040.302Y-100000@thelab.hub.org>

> On Sat, 18 Apr 1998, Byron Nikolaidis wrote:
> 
> > 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.
> 
> 	And I've have to say a *definite* no here...the result of that
> would be two different drivers, with different features available to
> it...totally unacceptable.
> 

Why?

Pretty much every product that I can think of has separate 16-bit and 32-bit 
product groups.

Albeit that most of those are MS products, there is no real reason why 
different environments should not have different solutions.

The ODBC spec is well defined so anything conforming to it should be 
reasonably feature-compatible. 

> 	That would be like taking our 32bit vs 64bit server and saying
> that since nobody many ppl are using 64bit right now, we're going to get
> rid of those features that are currently broken, instead of trying to
> address them.
> 

Not a good example I think. The 16/32-bit ODBC question says nothing about 
dropping features. As I said above, ODBC is ODBC: you either conform or you 
don't. If there happen to be differences between the levels of conformance or 
of performance between 16 and 32-bit models, that would be a pity but not 
earth shattering.

Next you will want to ban anything that behaves/performs  differently on NT 
than on UNIX;-)

> 	Quite frankly, this whole thread is starting to cause me to
> reconsider my decision to move away from the old driver over to this new
> driver... *sigh*
> 
>  Marc G. Fournier                                
> Systems Administrator @ hub.org 
> primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 
> 

Cheers,
Stephen


========================================================================
Stephen Davies Consulting	    		                            scldad@sdc.com.au
Adelaide, South Australia.     			                            Voice: 61-8-82728863
Computing & Network solutions.	 	                            Fax: 61-8-82741015





view thread (16+ messages)  latest in thread

Message-ID: <199804191234.WAA09636@mustang.sdc.com.au>
Permalink:  ../199804191234.WAA09636@mustang.sdc.com.au/
Also on:    postgresql.org/message-id/199804191234.WAA09636@mustang.sdc.com.au

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: scldad@sdc.com.au, scrappy@hub.org
  Subject: Re: [INTERFACES] Re: ODBC 16 bit support
  In-Reply-To: <199804191234.WAA09636@mustang.sdc.com.au>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox