Re: Frontend/Backend protocol 3.0

#1 (**permalink**) 04-16-2008, 02:12 AM

> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org
> [mailto

gsql-odbc-owner@postgresql.org] On Behalf Of Sivakumar K
> 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 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode