Re: Recommended ODBC version for compilation

Hi Dave/Peter,

Dave: As you know, we have spent quite a long time preparing the gap
analysis document between version 3.0 and 3.5x, and there was no
response at all to that :-(

> > there is support for features up to 0x0351 in some places.  Why are
> > they not enabled by default and/or what would be the ramifications
of
> > enabling them (say, using --with-odbcver)?

I do not know why they are not enabled by default, but you should be
able to enable them using --with-odbcver=0x0351.

We have not implemented any additional APIs in the libpq version. All
the APIs are the same as in the old driver. If somebody is interested,
they can go through the gap analysis document and suggest some useful
APIs to add, so that someone could take it up and work on that.

The gap analysis document can be found here:
http://pgfoundry.org/docman/view.php/1000125/82/psqlodbc3.5xcompliance.x
ls

Regards,
Anoop

> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org [mailto:pgsql-odbc-
> owner@postgresql.org] On Behalf Of Dave Page
> Sent: Saturday, November 12, 2005 7:36 PM
> To: Peter Eisentraut; pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] Recommended ODBC version for compilation
>
>
>
>
> On 12/11/05 1:36 pm, "Peter Eisentraut" <peter_e@gmx.net> wrote:
>
> > It seems the default ODBC version continues to be 0x0300 even though
> > there is support for features up to 0x0351 in some places.  Why are
> > they not enabled by default and/or what would be the ramifications
of
> > enabling them (say, using --with-odbcver)?
>
> I'm not entirely sure what the ramifications will be - I can't imagine
it
> will cause many problems provided apps interogate the driver before
using
> advanced features (as they really should anyway).
>
> Anoop can probably answer more as he's spent quite some time looking
at
> our
> spec compliance - have you seen his gap analysis on the pgFoundry
site?
>
> Regards, Dave
>
>
>
> ---------------------------(end of
broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
>                http://archives.postgresql.org