Re: int8 becames string in BDE :-( - Mailing list pgsql-odbc

From Dave Page
Subject Re: int8 becames string in BDE :-(
Date
Msg-id D85C66DA59BA044EB96AB9683819CF610150BF@dogbert.vale-housing.co.uk
Whole thread Raw
In response to int8 becames string in BDE :-(  (Kovacs Zoltan <kovacsz@pc10.radnoti-szeged.sulinet.hu>)
List pgsql-odbc

> -----Original Message-----
> From: SZ?CS Gabor [mailto:surrano@mailbox.hu]
> Sent: 04 June 2002 12:40
> To: pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] int8 becames string in BDE :-(
>
>
> Gabor here, from own address -- thanks for CC'ing. please keep on.
>
> Well, last we discussed driver GUI problems; here is an
> extreme request about the new int8 return type option:
>
> Is it possible, and, if not a significant work, would you
> (Hiroshi) add another choice, namely, int4? (argh :) ) It
> would be a real quick fix to our problem to help change
> between the databases.

What's wrong with int4? I don't recall hearing of any problems with them
in the last 5 years or so. If this request is to make your life easier
on your current project rather than fix an actual bug, then I would
strongly object to adding such a hack to the driver and would suggest
that you take a copy of the source and look into hacking it yourself.
The code in question is in pgtypes.c - the int8 hacks have the comment
/* Change this to SQL_BIGINT for ODBC v3 bjm 2001-01-23 */ above them
for reference.

Regards, Dave.

pgsql-odbc by date:

Previous
From: SZ?CS Gabor
Date:
Subject: Re: int8 becames string in BDE :-(
Next
From: Hiroshi Inoue
Date:
Subject: Re: int8 becames string in BDE :-(