Re: Frontend/Backend protocol 3.0

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Jonathan Fuerth" <fuerth(at)sqlpower(dot)ca>, "Sivakumar K" <sivakumark(at)pervasive-postgres(dot)com>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: Frontend/Backend protocol 3.0
Date: 2005-06-07 15:13:28
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E490E377@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Jonathan Fuerth
> Sent: 07 June 2005 15:39
> To: Sivakumar K
> Cc: <pgsql-odbc(at)postgresql(dot)org>
> Subject: Re: [ODBC] Frontend/Backend protocol 3.0
>
> 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?

Well, I'm dealing with Anoop Kumar who was working on this (I assume
Sivakumar is a colleague), but yes, following review on the list if the
patch looks OK I will commit it.

Regards, Dave.

Browse pgsql-odbc by date

  From Date Subject
Next Message Steve Poe 2005-06-08 00:02:38 ODBC Compatibility with AMD64
Previous Message Jonathan Fuerth 2005-06-07 14:38:52 Re: Frontend/Backend protocol 3.0