| From: | Nick Gorham <nick(at)easysoft(dot)com> |
|---|---|
| To: | Peter Harvey <pharvey(at)codebydesign(dot)com> |
| Cc: | Andrew Bell <acbell(at)iastate(dot)edu>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: long ints use for 4-byte entities in ODBC |
| Date: | 2001-12-20 11:41:43 |
| Message-ID: | 3C21CE77.42B7419@easysoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Harvey wrote:
> > I was installing the ODBC driver on an alpha box. Problem is that there
> > are assumptions in the typedefs that a four byte integer is a "long
> > int". Of course, this is often an incorrect assumption. I can fix this,
> > but wanted to know how people wanted this done. How do you handle this
> > issue in the server? Seems confingure.in and associated files is the most
> > reasonable way to fix this to me.
>
> Also; which driver manager are you using? I think Nick Gorham has been
> working on this issue within unixODBC.
>
> Peter
AFAIK there should be nothing wrong with
typedef Int4 int
instead of the
typedef Int4 long
which is plainly wrong on 64 bit platforms.
--
Nick Gorham
Easysoft Ltd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karel Zak | 2001-12-20 13:53:07 | tkConfig.sh vs. ./configure |
| Previous Message | Thomas Lockhart | 2001-12-20 05:25:39 | Re: datetime and timespan deprecated |