FW: Problems with int8 and MS ADO/ODBC (inc patch)

From: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
To: "'pgsql-interfaces(at)postgresql(dot)org'" <pgsql-interfaces(at)postgresql(dot)org>
Subject: FW: Problems with int8 and MS ADO/ODBC (inc patch)
Date: 2000-12-22 09:32:28
Message-ID: 8568FC767B4AD311AC33006097BCD3D61A282C@woody.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces


> -----Original Message-----
> From: Ken J. Wright [mailto:ken(at)ori-ind(dot)com]
> Sent: 21 December 2000 20:44
> To: Dave Page
> Subject: Re: [INTERFACES] Problems with int8 and MS ADO/ODBC
>
>
> Depending on how strict ado is about odbc versioning, the
> problem can be
> because an int8 type now returns an integer value (bigint)
> via odbc as per odbc
> v3.0. However the driver reports itself as v2.0, which is
> supposed to return a
> sting for a bigint column. This was changed in the driver a
> while back to
> satisfy complaints about returning a string for a bigint
> column. It really
> should be changed back to the v2.0 spec, as the driver is not
> 3.0 compliant.

Thanks Ken, I just modified the ODBC code so int8 returns SQL_CHAR and it
works great. I've attached a patch for anyone that wants it.

Regards,

Dave.

Attachment Content-Type Size
patch.diff application/octet-stream 3.9 KB

Browse pgsql-interfaces by date

  From Date Subject
Next Message Michael Meskes 2000-12-22 12:44:02 Re: Problem with ecpg and 7.1beta1
Previous Message Peter Mount 2000-12-22 08:38:08 RE: [INTERFACES] Bugs in 7.1beta JDBC driver