RE: Win ODBC drivers for Postgres - Mailing list pgsql-interfaces

From Peter Mount
Subject RE: Win ODBC drivers for Postgres
Date
Msg-id 1B3D5E532D18D311861A00600865478CF1AEDE@EXCHANGE1
Whole thread Raw
In response to Win ODBC drivers for Postgres  (Mihai Gheorghiu <tanhq@bigplanet.com>)
List pgsql-interfaces
See below...

--
Peter Mount
Enterprise Support
Maidstone Borough Council
Any views stated are my own, and not those of Maidstone Borough Council

> -----Original Message-----
> From:    Byron Nikolaidis [SMTP:byron.nikolaidis@home.com]
> Sent:    Wednesday, June 07, 2000 10:31 PM
> To:    Mihai Gheorghiu; pgsql-interfaces@postgresql.org
> Subject:    Re: [INTERFACES] Win ODBC drivers for Postgres
> 
> Hey there partner,
> 
> To quote the immortal Butthead:  "uhhhh....................., ok."
> 
> Seriously, I wonder how this "consultant" came up with this?   Sounds
> awefully generalized.   I think I could say that line about anything,
> including ODBC itself.[Peter Mount]  I can think of a few non-public domain items that are
even worse...

> Also, many of the compromises of the ODBC driver are based on shortcomings
> of the backend.  Jeez, we still "simulate" a Prepared Statement because
> there isn't one in the backend.   Is the backend ever gonna have
> this?AFAIK,
> the JDBC driver simulates the prepared statement also.
> [Peter Mount]  Yes, JDBC does simulate prepared statements, but as
soon as the backend supports it (which, some one correct me, may be possible
after a parser rewrite?) it will be changed over. This is one of the big
performance hits in JDBC at the moment.

> Some may remember the "declare/fetch" feature of the ODBC driver, that
> makes
> use of postgres cursors.  This feature was added to help with the network
> bandwidth problem -- instead of getting the entire query result, it
> fetched
> it in chunks when required.
> [Peter Mount]  I want to add this capability to JDBC, especially the
JDBC2 driver, as it's ResultSet can implicitly handle cursors. I was
originally going to do it for 7.0.

> Yeah, so maybe connection pooling would be nice, but most things use one
> or
> two connections don't they?   Do most processes keep asking odbc for a new
> connection?[Peter Mount]  I'm not sure about ODBC, but in JDBC a lot of people
use connection pools, especially with Servlets or CORBA applications.

> Byron
> 
> ----- Original Message -----
> From: Mihai Gheorghiu <tanhq@bigplanet.com>
> To: <pgsql-interfaces@postgresql.org>
> Sent: Wednesday, June 07, 2000 10:36 AM
> Subject: [INTERFACES] Win ODBC drivers for Postgres
> 
> 
> > The following is a quote from a consultant's opinion on my intention to
> > migrate to Postgresql.
> > Quote:
> > [ODBC public domain drivers] are immature, inefficient and are network
> > bandwidth hogs. The public domain drivers don't support connection
> caching
> > which reuses an existing database connection for same queries to reduce
> the
> > query result time.
> > Unquote.
> > Please comment.
> >
> > Best regards,
> >
> > Mihai
> >
> > PS See also pgsql-general for opinion on Postgres :-)
> >


pgsql-interfaces by date:

Previous
From: "Sam O'Connor"
Date:
Subject: Re: Win ODBC drivers for Postgres
Next
From: Nicolas Huillard
Date:
Subject: RE: Win ODBC drivers for Postgres