From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Reshat Sabiq" <sabiq(at)purdue(dot)edu>, <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: int types migrated one level lower |
Date: | 2002-12-29 21:39:42 |
Message-ID: | 03AF4E498C591348A42FC93DEA9661B8128DF0@mail.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
> -----Original Message-----
> From: Reshat Sabiq [mailto:sabiq(at)purdue(dot)edu]
> Sent: 29 December 2002 21:34
> To: Dave Page; pgadmin-support(at)postgresql(dot)org
> Subject: Re: [pgadmin-support] int types migrated one level lower
>
>
> What I meant to say is that there is nothing wrong with
> either ADO's, or pgAdmin's mappings. The problem arises from
> the fact that MS Access has a "downward-revised" mapping of
> integer types: byte - 8 bits (this one is fine) integer - 16
> bits (i.e., int2, but normally should be int4) long integer -
> 32 bits (i.e., int4, but normally should be int8)
Ahh, I see. Thanks for clarifying what you meant.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Cheryl Thompson | 2002-12-31 22:05:20 | Can't see any tables?? |
Previous Message | Reshat Sabiq | 2002-12-29 21:34:28 | Re: int types migrated one level lower |