| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org> |
| Subject: | Re: Removing support for v1 and v2 protocols? |
| Date: | 2014-06-19 13:03:37 |
| Message-ID: | 20140619130337.GQ16098@tamriel.snowman.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
* Dave Page (dpage(at)pgadmin(dot)org) wrote:
> On Thu, Jun 19, 2014 at 4:49 AM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> > I'm a bit lost as to why psqlODBC does so much of this its self, instead
> > of just using libpq. PgJDBC does it because it wants to be a JDBC Type 4
> > driver, i.e. all Java code, so it can't talk to libpq over JNI/JNA. That
> > concern does not apply to psqlODBC, which in fact already links to libpq
> > but doesn't seem to use it for protocol handling.
>
> We tried to port psqlODBC to libpq 5 - 10 years ago. It didn't go
> well, and eventually we went back to the original code.
As I recall, one big issue about porting to libpq was the lack of a
streaming-style capability without using cursors. We have the 'single
row mode' option in libpq now which might address that. I'm sure there
were other issues but I don't recall them offhand.
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Barry Bell | 2014-06-19 15:14:08 | Out of memory while reading tuples error |
| Previous Message | Heikki Linnakangas | 2014-06-19 12:33:06 | Re: Problem in SQLFreeHandle (Statement) |