RE: Re: [HACKERS] ODBC Driver int8 Patch - Mailing list pgsql-patches

From Dave Page
Subject RE: Re: [HACKERS] ODBC Driver int8 Patch
Date
Msg-id 8568FC767B4AD311AC33006097BCD3D61A2907@woody.vale-housing.co.uk
Whole thread Raw
List pgsql-patches

> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: 23 January 2001 17:38
> To: Bruce Momjian
> Cc: Dave Page; pgsql-odbc@postgresql.org; PostgreSQL-patches
> Subject: Re: [PATCHES] Re: [HACKERS] ODBC Driver int8 Patch
>
>
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > I am waiting for someone to comment on this.  Anyone?
>
> Seems like we need a policy decision: do we want to try to be
> ODBC v2 or
> v3?  I don't know what else we might have to change if we want to be
> v3-compliant, so that seems like a risky way to proceed right before
> a release ...

What advantages would be gained from going to V3 for end users/developers?
Perhaps more importantly, who would be able to do the work? I know Julie
offered to work on the driver, but other than a message a few weeks ago to
say hello I've heard nothing.

I would vote to stick with v2.5 for now but get things like query length,
max tuple size, outer joins (see my message from yesterday) and anything
else that may cause problems for people sorted out.

Regards,

Dave.

pgsql-patches by date:

Previous
From: Ian Lance Taylor
Date:
Subject: Support for cursors in PL/pgSQL
Next
From: Tom Lane
Date:
Subject: Re: Small patch to replace 'idle' by 'trans' if transactionis still open