int types migrated one level lower - Mailing list pgadmin-support

From Reshat Sabiq
Subject int types migrated one level lower
Date
Msg-id 000001c2ac19$54813930$da86d380@main
Whole thread Raw
In response to Re: Access-postgreSQL migration (extra invalid foreign key added)  ("Dave Page" <dpage@vale-housing.co.uk>)
List pgadmin-support
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. 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).

P.S. I'd like to suggest enhancements for pgAdmin3:
1) getting integer to map into int4
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.

Sincerely,
r.





pgadmin-support by date:

Previous
From: "Dave Page"
Date:
Subject: Re: Bug for view with rules
Next
From: Didier Moens
Date:
Subject: Re: pgAdminII 1.4.12 crash with PostgreSQL 7.3