pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedodbc V3+
3+ messages / 3 participants
[nested] [flat]
* odbc V3+
@ 1999-08-19 23:29 Paul <hardiman@hardiman.com>
1999-08-26 17:18 ` Re: [INTERFACES] odbc V3+ Byron Nikolaidis <byron.nikolaidis@home.com>
0 siblings, 1 reply; 3+ messages in thread
From: Paul @ 1999-08-19 23:29 UTC (permalink / raw)
To: pgsql-interfaces
Hello,
Any scuttle butt on when the Postgresql odbc will move from 2 to 3?
Thanks
--
Regards,
Paul Hardiman
InterMedia, Inc (Colorado)
Informations Systems Consulting
303-581-0606, Fax 581-0506, hardiman@hardiman.com
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: [INTERFACES] odbc V3+
1999-08-19 23:29 odbc V3+ Paul <hardiman@hardiman.com>
@ 1999-08-26 17:18 ` Byron Nikolaidis <byron.nikolaidis@home.com>
0 siblings, 0 replies; 3+ messages in thread
From: Byron Nikolaidis @ 1999-08-26 17:18 UTC (permalink / raw)
To: Paul <hardiman@hardiman.com>; +Cc: pgsql-interfaces
Paul wrote:
>
> Hello,
> Any scuttle butt on when the Postgresql odbc will move from 2 to 3?
>
> Thanks
>
> --
> Regards,
> Paul Hardiman
> InterMedia, Inc (Colorado)
> Informations Systems Consulting
> 303-581-0606, Fax 581-0506, hardiman@hardiman.com
>
> ************
Not very likely. The increased complexity between 2 and 3 would make
this a massive effort, for what I see as very little benefit.
Is there any specific thing in odbc 3.0 that you need? The driver
should still work with odbc 3.0 applications because the odbc driver
manager is supposed to convert calls to odbc 2.x on the fly. I'm not
sure how extensively it does this.
Byron
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: [INTERFACES] odbc V3+
@ 1999-09-01 20:32 blackw@sfu.ca
0 siblings, 0 replies; 3+ messages in thread
From: blackw@sfu.ca @ 1999-09-01 20:32 UTC (permalink / raw)
To: pgsql-interfaces
Paul wrote:
> Any scuttle butt on when the Postgresql odbc will move from 2 to 3?
To which Byron replied:
> Not very likely. [SNIP-O-RAMA] The driver
> should still work with odbc 3.0 applications because the odbc driver
> manager is supposed to convert calls to odbc 2.x on the fly. I'm not
> sure how extensively it does this.
I'd like to know where you came across this information, as I have not been able to confirm anywhere that a driver manager will perform the conversion you suggest. Quite to the contrary, I have found the following statement in Microsoft documentation:
"Applications that follow the ODBC 3.x specification must use conditional code to avoid using functionality new to ODBC 3.x when working with ODBC 2.x drivers. ODBC 2.x drivers do not support functionality new to ODBC 3.x just because the application declares that it follows the ODBC 3.x specification."
(MSDN Library - April 1999/
Platform SDK/
Data Access Services/
Microsoft Data Access 2.1 SDK/
Microsoft Open Database Connectivity (ODBC)/
Part 2 Developing Applications and Drivers/
Chapeter 6: Connecting to a Data Source or Driver/
Page: Delcaring the Application's ODBC Version
)
So, if you have a resource that indicates the contrary, I'd sure like to get my hands on it. Thanks.
Cheers,
Richard Blackwell
Programmer/Analyst
Dept. of Psychology, Simon Fraser University
Burnaby, BC Canada
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~1999-09-01 20:32 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-08-19 23:29 odbc V3+ Paul <hardiman@hardiman.com>
1999-08-26 17:18 ` Byron Nikolaidis <byron.nikolaidis@home.com>
1999-09-01 20:32 Re: [INTERFACES] odbc V3+ blackw@sfu.ca
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