From: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | ODBC Driver int8 Patch |
Date: | 2001-01-15 08:57:04 |
Message-ID: | 8568FC767B4AD311AC33006097BCD3D61A2875@woody.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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;
From | Date | Subject | |
---|---|---|---|
Next Message | Zeugswetter Andreas SB | 2001-01-15 09:31:23 | AW: CRCs |
Previous Message | Lamar Owen | 2001-01-15 07:24:19 | RPMS for 7.1beta3 being uploaded. |