From: | "Ansley, Michael" <Michael(dot)Ansley(at)intec(dot)co(dot)za> |
---|---|
To: | "'Thomas Lockhart'" <lockhart(at)alumni(dot)caltech(dot)edu>, "Ansley, Michael" <Michael(dot)Ansley(at)intec(dot)co(dot)za> |
Cc: | "'pgsql-interfaces(at)postgresql(dot)org'" <pgsql-interfaces(at)postgreSQL(dot)org> |
Subject: | RE: [INTERFACES] SSL and ODBC |
Date: | 1999-10-01 07:25:27 |
Message-ID: | 1BF7C7482189D211B03F00805F8527F748C0EF@S-NATH-EXCH2 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)alumni(dot)caltech(dot)edu]
>> Sent: Friday, October 01, 1999 4:50 AM
>> To: Ansley, Michael
>> Cc: 'pgsql-interfaces(at)postgresql(dot)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(at)alumni(dot)caltech(dot)edu
>> South Pasadena, California
>>
>> ************
>>
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 1999-10-01 07:58:35 | RE: [INTERFACES] SSL and ODBC |
Previous Message | Thomas Lockhart | 1999-10-01 02:50:05 | Re: [INTERFACES] SSL and ODBC |