ODBC Driver int8 Patch - Mailing list pgsql-hackers

From Dave Page
Subject ODBC Driver int8 Patch
Date
Msg-id 8568FC767B4AD311AC33006097BCD3D61A2875@woody.vale-housing.co.uk
Whole thread Raw
Responses Re: ODBC Driver int8 Patch  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Hi,

It was suggested that I post this patch here as no notice was taken of it
when posted to interfaces!

This fixes problems with int8 columns which are reported by the driver as
SQL_BIGINT rather than SQL_CHAR as per the ODBC v2 spec. Specifically, I
have had problems with MS ADO - any queries that contain an int8 column in
the resultset will *always* return an empty recordset.

Regards,

Dave.

*** pgtypes.c.orig      Fri Dec 22 09:12:22 2000
--- pgtypes.c   Fri Dec 22 09:12:22 2000
***************
*** 217,223 ****       case PG_TYPE_XID:       case PG_TYPE_INT4:          return SQL_INTEGER;

!       case PG_TYPE_INT8:                      return SQL_BIGINT;       case PG_TYPE_NUMERIC:           return
SQL_NUMERIC;
       case PG_TYPE_FLOAT4:        return SQL_REAL;
--- 217,223 ----       case PG_TYPE_XID:       case PG_TYPE_INT4:          return SQL_INTEGER;

!       case PG_TYPE_INT8:                      return SQL_CHAR;       case PG_TYPE_NUMERIC:           return
SQL_NUMERIC;
       case PG_TYPE_FLOAT4:        return SQL_REAL;


pgsql-hackers by date:

Previous
From: Emmanuel Charpentier
Date:
Subject: Re: MS Access vs IS NULL (was Re: [BUGS] Bug in SQL functions that use a NULL parameter directly)
Next
From: Rehak Tamas
Date:
Subject: Re: copy from stdin; bug?