Re: migration problems with 1.3.60 alpha + gui issues

> -----Original Message-----
> From: Armbrust, Daniel C. [mailto:Armbrust.Daniel@mayo.edu]
> Sent: 14 August 2002 18:37
> To: pgadmin-support@postgresql.org
> Subject: [pgadmin-support] migration problems with 1.3.60
> alpha + gui issues
>
>
> When attempting to migrate a set of tables from an access
> database using version 1.3.60 alpha, According to the log
> file, the following SQL was generated:
>
> SELECT MAX(`OID_key`) AS RECCOUNT FROM `OID_root`CREATE
> SEQUENCE "OID_root_OID_key_key" START 356

This syntax is legal on Access - does the log say it's being executed
against PostgreSQL?

> Additionally, in version 1.3.60 alpha, when I launch the
> program, the lower right pane where "Definition" is does not
> get painted until I click on something that causes data to go
> there.  It stays transparent at first (I can see my desktop
> through it)

That's definately wierd. It's also handled by VB so there's not much I
can do. I guess I could write a string there at startup.

>
> Last:
> In version the new version, when I connect to my database, it
> doesn't show me any of my tables with the new version.  I
> believe that this may have something to do with the fact that
> my table names contain capital letters (I'm new to postgres,
> is uppercase and postgres a bad thing?) - however, this works
> in the old version.  I'm currently testing the capital letter
> theory.  It appears that the calls must be surrounded in
> quotes?  And the new version is not doing it?

I would avoid capitals if possible. Stick to a-z, 0-9 and _

In this version tables are listed under a dummy schema, so make sure you
expand Schemas -> Public in the treeview. This new structure is designed
for PostgreSQL 7.3, but with maximum backward compatibility without
things getting overly complex.

Regards, Dave.