This is a discussion on Re: Frontend/Backend protocol 3.0 within the pgsql Interfaces odbc forums, part of the PostgreSQL category; --> We too don't want to do so. However until the testing of new libpq odbc driver is completed, the ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| 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. Regards, Siva Kumar.K -----Original Message----- From: Dave Page [mailto:dpage@vale-housing.co.uk] Sent: Tuesday, June 07, 2005 3:01 PM To: Sivakumar K; pgman@candle.pha.pa.us; fuerth@sqlpower.ca Cc: jd@commandprompt.com; pgsql-odbc@postgresql.org Subject: RE: [ODBC] Frontend/Backend protocol 3.0 > -----Original Message----- > From: pgsql-odbc-owner@postgresql.org > [mailto > Sent: 07 June 2005 09:44 > To: pgman@candle.pha.pa.us; fuerth@sqlpower.ca > Cc: jd@commandprompt.com; pgsql-odbc@postgresql.org > Subject: Re: [ODBC] Frontend/Backend protocol 3.0 > > Hi all, > > In continuation to my previous mail, here is an overview on > the approach > that we have taken. We had a few design goals when we started on this > exercise. > > 1. ODBC driver should still support socket mode. > 2. Use if-defs minimally. > 3. The code change should be minimal. > 4. Use a compile time flag USE_LIBPQ to switch between libPQ > and socket. Why keep the socket stuff? The whole point is to get rid of it and the associated complexity and rely on libpq. Regards, Dave. ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq |
| ||||
| 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 ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings |