pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedSSL and ODBC
6+ messages / 4 participants
[nested] [flat]
* SSL and ODBC
@ 1999-09-30 11:45 Ansley, Michael <Michael.Ansley@intec.co.za>
0 siblings, 1 reply; 6+ messages in thread
From: Ansley, Michael @ 1999-09-30 11:45 UTC (permalink / raw)
To: pgsql-interfaces
I presume that the ODBC driver uses libpq underneath (either statically or
dynamically loaded) to talk to the server. That being the case, is it
possible to enable the existing SSL links (probably very experimental at the
moment) between the client and server while using ODBC? This would be a BIG
win.
MikeA
--------------------------------------------------------------------
Science is the game we play with God to find out what his rules are.
--------------------------------------------------------------------
[(LI)U]NIX IS user friendly; it's just picky about who its friends are.
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: [INTERFACES] SSL and ODBC
@ 1999-10-01 02:50 Thomas Lockhart <lockhart@alumni.caltech.edu>
parent: Ansley, Michael <Michael.Ansley@intec.co.za>
0 siblings, 0 replies; 6+ messages in thread
From: Thomas Lockhart @ 1999-10-01 02:50 UTC (permalink / raw)
To: Ansley, Michael <Michael.Ansley@intec.co.za>; +Cc: pgsql-interfaces
> I presume that the ODBC driver uses libpq underneath (either statically or
> dynamically loaded) to talk to the server.
Actually, no! libpq requires a cygwin environment, and (perhaps) there
was a worry about performance (though that doesn't seem to be an issue
to me). So the ODBC driver is completely standalone. The downside is
that it requires separate maintenance, and I'm pretty sure that there
are some arcane issues which don't get fixed there when they change in
libpq...
- Thomas
--
Thomas Lockhart lockhart@alumni.caltech.edu
South Pasadena, California
^ permalink raw reply [nested|flat] 6+ messages in thread
* RE: [INTERFACES] SSL and ODBC
@ 1999-10-01 07:25 Ansley, Michael <Michael.Ansley@intec.co.za>
0 siblings, 0 replies; 6+ messages in thread
From: Ansley, Michael @ 1999-10-01 07:25 UTC (permalink / raw)
To: 'Thomas Lockhart' <lockhart@alumni.caltech.edu>; Ansley, Michael <Michael.Ansley@intec.co.za>; +Cc: pgsql-interfaces
So how difficult would it be to include the SSL stuff in the ODBC drivers.
MikeA
>> -----Original Message-----
>> From: Thomas Lockhart [mailto:lockhart@alumni.caltech.edu]
>> Sent: Friday, October 01, 1999 4:50 AM
>> To: Ansley, Michael
>> Cc: 'pgsql-interfaces@postgresql.org'
>> Subject: Re: [INTERFACES] SSL and ODBC
>>
>>
>> > I presume that the ODBC driver uses libpq underneath
>> (either statically or
>> > dynamically loaded) to talk to the server.
>>
>> Actually, no! libpq requires a cygwin environment, and
>> (perhaps) there
>> was a worry about performance (though that doesn't seem to
>> be an issue
>> to me). So the ODBC driver is completely standalone. The downside is
>> that it requires separate maintenance, and I'm pretty sure that there
>> are some arcane issues which don't get fixed there when they
>> change in
>> libpq...
>>
>> - Thomas
>>
>> --
>> Thomas Lockhart
>> lockhart@alumni.caltech.edu
>> South Pasadena, California
>>
>> ************
>>
^ permalink raw reply [nested|flat] 6+ messages in thread
* RE: [INTERFACES] SSL and ODBC
@ 1999-10-01 07:58 Magnus Hagander <mha@sollentuna.net>
0 siblings, 0 replies; 6+ messages in thread
From: Magnus Hagander @ 1999-10-01 07:58 UTC (permalink / raw)
To: 'Thomas Lockhart' <lockhart@alumni.caltech.edu>; Ansley, Michael <Michael.Ansley@intec.co.za>; +Cc: pgsql-interfaces
> > I presume that the ODBC driver uses libpq underneath
> (either statically or
> > dynamically loaded) to talk to the server.
>
> Actually, no! libpq requires a cygwin environment, and (perhaps) there
> was a worry about performance (though that doesn't seem to be an issue
> to me). So the ODBC driver is completely standalone. The downside is
> that it requires separate maintenance, and I'm pretty sure that there
> are some arcane issues which don't get fixed there when they change in
> libpq...
No, that is not correct. libpq does *not* require the cygwin environment -
it can also be compiled as native Win32.
However, the ODBC driver still does not use libpq, because when the ODBC
driver was born, libpq did not exist on Win32.
//Magnus
^ permalink raw reply [nested|flat] 6+ messages in thread
* RE: [INTERFACES] SSL and ODBC
@ 1999-10-01 16:21 Ken J. Wright <ken@ori-ind.com>
0 siblings, 0 replies; 6+ messages in thread
From: Ken J. Wright @ 1999-10-01 16:21 UTC (permalink / raw)
To: pgsql-interfaces
At 09:58 10/01/1999 +0200, Magnus Hagander wrote:
>> > I presume that the ODBC driver uses libpq underneath
>> (either statically or
>> > dynamically loaded) to talk to the server.
>>
>> Actually, no! libpq requires a cygwin environment, and (perhaps) there
>> was a worry about performance (though that doesn't seem to be an issue
>> to me). So the ODBC driver is completely standalone. The downside is
>> that it requires separate maintenance, and I'm pretty sure that there
>> are some arcane issues which don't get fixed there when they change in
>> libpq...
>
>No, that is not correct. libpq does *not* require the cygwin environment -
>it can also be compiled as native Win32.
>However, the ODBC driver still does not use libpq, because when the ODBC
>driver was born, libpq did not exist on Win32.
Just a bit of archive history about psqlodbc from, 8/98.
David Hartwig's response to Thomas Lockhart.
[snip]
> btw, I've only just started looking at the fe/be code, but istm that it
> would be really nice if libpq-fe could fully support the WIN32 interface
> or if psqlodbc could use libpq-fe when on a Unix box. Some guy in Russia
> has a driver which uses libpq-fe and the code looks like it has the same
> lineage as Byron's code (before Byron started working on it). Where does
> this code come from? Byron's code gives credit to Christian Czezatke and
> Dan McGuirk but the "iodbc project" driver doesn't.
>
Don't know about the Russian dude, but the we completely rewrote the the
front-end section in the driver. We did not (and still do not) like the
way libpq consumes the entire query result into front-end memory before
returning control to the application. This make large queries slow and
sometimes impossible. However, with the patches that Bruce and Vadim are
working on for multiple ORs (many thanks) this may become a moot issue.
[endsnip]
^ permalink raw reply [nested|flat] 6+ messages in thread
* RE: [INTERFACES] SSL and ODBC
@ 1999-10-03 12:25 Ansley, Michael <Michael.Ansley@intec.co.za>
0 siblings, 0 replies; 6+ messages in thread
From: Ansley, Michael @ 1999-10-03 12:25 UTC (permalink / raw)
To: 'Ken J. Wright' <ken@ori-ind.com>; pgsql-interfaces
Yes, of course, consuming the entire query is a problem; I hadn't thought
about that, although, I had noticed it as a problem with libpq before.
How are the multiple OR changes going to affect this?
MikeA
>> -----Original Message-----
>> From: Ken J. Wright [mailto:ken@ori-ind.com]
>> Sent: Friday, October 01, 1999 6:21 PM
>> To: pgsql-interfaces@postgreSQL.org
>> Subject: RE: [INTERFACES] SSL and ODBC
>>
>>
>> At 09:58 10/01/1999 +0200, Magnus Hagander wrote:
>> >> > I presume that the ODBC driver uses libpq underneath
>> >> (either statically or
>> >> > dynamically loaded) to talk to the server.
>> >>
>> >> Actually, no! libpq requires a cygwin environment, and
>> (perhaps) there
>> >> was a worry about performance (though that doesn't seem
>> to be an issue
>> >> to me). So the ODBC driver is completely standalone. The
>> downside is
>> >> that it requires separate maintenance, and I'm pretty
>> sure that there
>> >> are some arcane issues which don't get fixed there when
>> they change in
>> >> libpq...
>> >
>> >No, that is not correct. libpq does *not* require the
>> cygwin environment -
>> >it can also be compiled as native Win32.
>> >However, the ODBC driver still does not use libpq, because
>> when the ODBC
>> >driver was born, libpq did not exist on Win32.
>>
>>
>> Just a bit of archive history about psqlodbc from, 8/98.
>> David Hartwig's response to Thomas Lockhart.
>>
>> [snip]
>> > btw, I've only just started looking at the fe/be code, but
>> istm that it
>> > would be really nice if libpq-fe could fully support the
>> WIN32 interface
>> > or if psqlodbc could use libpq-fe when on a Unix box. Some
>> guy in Russia
>> > has a driver which uses libpq-fe and the code looks like
>> it has the same
>> > lineage as Byron's code (before Byron started working on
>> it). Where does
>> > this code come from? Byron's code gives credit to
>> Christian Czezatke and
>> > Dan McGuirk but the "iodbc project" driver doesn't.
>> >
>>
>> Don't know about the Russian dude, but the we completely
>> rewrote the the
>> front-end section in the driver. We did not (and still do
>> not) like the
>> way libpq consumes the entire query result into front-end
>> memory before
>> returning control to the application. This make large
>> queries slow and
>> sometimes impossible. However, with the patches that Bruce
>> and Vadim are
>> working on for multiple ORs (many thanks) this may become a
>> moot issue.
>> [endsnip]
>>
>>
>>
>> ************
>>
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~1999-10-03 12:25 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-09-30 11:45 SSL and ODBC Ansley, Michael <Michael.Ansley@intec.co.za>
1999-10-01 02:50 ` Thomas Lockhart <lockhart@alumni.caltech.edu>
1999-10-01 07:25 RE: [INTERFACES] SSL and ODBC Ansley, Michael <Michael.Ansley@intec.co.za>
1999-10-01 07:58 RE: [INTERFACES] SSL and ODBC Magnus Hagander <mha@sollentuna.net>
1999-10-01 16:21 RE: [INTERFACES] SSL and ODBC Ken J. Wright <ken@ori-ind.com>
1999-10-03 12:25 RE: [INTERFACES] SSL and ODBC Ansley, Michael <Michael.Ansley@intec.co.za>
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