| From: | Magnus Hagander <mha(at)sollentuna(dot)net> |
|---|---|
| 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:58:35 |
| Message-ID: | 215896B6B5E1CF11BC5600805FFEA82101F7131A@sirius.edu.sollentuna.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | SAKAIDA | 1999-10-01 08:24:57 | pgbash-1.1.1 release |
| Previous Message | Ansley, Michael | 1999-10-01 07:25:27 | RE: [INTERFACES] SSL and ODBC |