RE: ODBC Driver int8 Patch

From: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
To: "'Bruce Momjian'" <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org>
Subject: RE: ODBC Driver int8 Patch
Date: 2001-01-16 17:07:36
Message-ID: 8568FC767B4AD311AC33006097BCD3D61A288C@woody.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: Bruce Momjian [mailto:pgman(at)candle(dot)pha(dot)pa(dot)us]
> Sent: 16 January 2001 16:50
> To: Dave Page
> Cc: 'pgsql-hackers(at)postgresql(dot)org'
> Subject: Re: [HACKERS] ODBC Driver int8 Patch
>
>
> As I remember, the problem is that this makes us match the
> ODBC v2 spec,
> but then we would not match the v3 spec. Is that correct?
>

Yes, the patch I supplied will make it correct for v2. As it stands it is
correct for v3. However as the driver identifies itself as v2 (i believe now
v2.5) compliant, ADO expects it to follow the v2 spec and then fails when it
doesn't.

The original problem was briefly discussed on the interfaces list under the
thread '[INTERFACES] Problems with int8 and MS ADO/ODBC'

Regards,

Dave.

Browse pgsql-hackers by date

  From Date Subject
Next Message Mikheev, Vadim 2001-01-16 17:18:56 RE: SIGTERM -> elog(FATAL) -> proc_exit() is probably a bad idea
Previous Message Bruce Momjian 2001-01-16 16:50:28 Re: ODBC Driver int8 Patch