| From: | Jonathan Fuerth <fuerth(at)sqlpower(dot)ca> |
|---|---|
| To: | "Sivakumar K" <sivakumark(at)pervasive-postgres(dot)com> |
| Cc: | <pgsql-odbc(at)postgresql(dot)org> <pgsql-odbc(at)postgresql(dot)org> |
| Subject: | Re: Frontend/Backend protocol 3.0 |
| Date: | 2005-06-07 14:38:52 |
| Message-ID: | 68eea00b98829d6af6fdea02093ce5ee@sqlpower.ca |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
On Jun 7, 2005, at 8:14 AM, Sivakumar K wrote:
> We too don't want to do so. However until the testing of new libpq odbc
> driver is completed, the user can have an option of using socket code
> or
> libpq code.
>
> Once the new libpq odbc driver is stable we can get rid of the socket
> stuff.
Sounds like I wasted four good days of effort last week. :)
Two questions:
Sivakumar: Will your upcoming libpq patch include support for getting
the SQLSTATE codes from backend to the ODBC side?
Dave: Will you commit Sivakumar's patch into the posqlodbc project?
Regards,
Jonathan Fuerth
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2005-06-07 15:13:28 | Re: Frontend/Backend protocol 3.0 |
| Previous Message | Dave Page | 2005-06-07 12:55:43 | Re: Frontend/Backend protocol 3.0 |