Re: int types migrated one level lower

Hi,
I do not have the source to hand, so please forgive any errors. Comments below are prefixed with DP

_____________Original message ____________
Subject: [pgadmin-support] int types migrated one level lower
Sender: "Reshat Sabiq" <sabiq(at)purdue(dot)edu>
Date: Thu, 26 Dec 2002 15:05:37 +0000

My integer types migrated from Access one level lower than is shown in
the Map in the wizard. Thus,
integer became int2 instead int4

Also, long integer became int4 instead int8, although long integer
wasn't in the map so that probably doesn't count formally.

DP: pgAdmin doesn't see the data types you see in Access, it sees the ADO datatypes listed on the type map dialogue. The differences you are seeing are almost certainly because ADO is not mapping the types exactly as you expect.

At the same
time, byte became int2, but apparently that is the only possible way
because I'm not seeing an 8-bit integer type in postgres (please let me
know if there is one).

DP: Isn't there byte in pg? I know there is bytea (array of byte).

P.S. I'd like to suggest enhancements for pgAdmin3:
1) getting integer to map into int4

DP: I don't have any intention of re-writing the migration wizard for pgAdmin 3 at the moment. If I did, the type mapping would be definable as it is now, but from ODBC types, not ADO.

2) adding a source type 'long integer' with a mapping to int8.
In the long run, it would also be nice to have an 8-bit integer type if
there isn't one yet.

DP: We don't define the source types, and the target types come straight from PostgreSQL.

Regards, Dave.