Обсуждение: problem adding a foreign key in v1.5 and a question re v1.5 vs 1.2.2

hi!

i'm using pgadmin3 v1.5 devel, built today from a fresh cvs checkout.

with this version i am having problems adding foreign keys (to existing 
tables or when creating a new table) since pgadmin doesn't seem to 
refresh the columns in the selected table and i cannot select a column 
to specify it as a referencing column. the pull-down list contains the 
name of the first column from the table which was selected by default 
when the dialog window opened.

i wanted to try it with v1.2.2 but that version no longer recognizes any 
information about the servers. it realizes that i have 2 servers on the 
list but instead of the server names the string "(:0)" is written and in 
the server properties all values are blank.

i find this a bit strange because i recall having no problems using 
either version of pgadmin a short while ago.

i am running pgadmin3 on suse linux 9.3. please tell me if you need me 
to provide additional information and / or images.

regards,
Miha

Miha Radej wrote:
> hi!
> 
> i'm using pgadmin3 v1.5 devel, built today from a fresh cvs checkout.
> 
> with this version i am having problems adding foreign keys (to existing 
> tables or when creating a new table) since pgadmin doesn't seem to 
> refresh the columns in the selected table and i cannot select a column 
> to specify it as a referencing column. 

Please specify the situation when you miss the columns.

the pull-down list contains the
> name of the first column from the table which was selected by default 
> when the dialog window opened.
> 
> i wanted to try it with v1.2.2 but that version no longer recognizes any 
> information about the servers. it realizes that i have 2 servers on the 
> list but instead of the server names the string "(:0)" is written and in 
> the server properties all values are blank.
> 
> i find this a bit strange because i recall having no problems using 
> either version of pgadmin a short while ago.

The registry format changed a day ago; the old was getting too crowded. 
1.5 will convert from older versions.

Regards,
Andresa

hi!

the foreign key problem seems to come from using an incorrect schema 
name. ie. in a database i am using i have a few schemas. i am working on 
one of them and when selecting a referencing table all table names are 
displayed as 'schema.tablename' except the tables from the current 
schema i'm working on, where just the form 'tablename' is used. and 
pgadmin3 appears to use the public schema if no schema seems to be 
specified, which then returns no columns.

ie: i am working on a schema called 'myschema' and i select a table 
'tablename' as a referenced table. pgadmin generates the following query 
to retrieve the column names from a newly selected table:
SELECT attname          FROM pg_attribute att, pg_class cl, pg_namespace nsp         WHERE attrelid=cl.oid AND
relnamespace=nsp.oid          AND nspname='public'           AND relname='tablename'           AND attnum > 0
 
         ORDER BY attnum

instead of
SELECT attname          FROM pg_attribute att, pg_class cl, pg_namespace nsp         WHERE attrelid=cl.oid AND
relnamespace=nsp.oid          AND nspname='myschema'           AND relname='tablename'           AND attnum > 0
 
         ORDER BY attnum

regards,
Miha

Hi list,

I can reproduce this error - could it be added as an
official bug, please?

I wish to create a foreign key on a table, referencing a
table in a schema that has the same name as my user id (my
personal schema). In the list of tables when adding the
foreign key ('References'), tables in my personal schema are
listed by table name, without the schema part. When choosing
such a table, the column list is empty.

The tables in my personal schema are in the search path, but
the column list apparently does not take that in account ?

regards, Sune B. Woeller


Miha Radej wrote:
> hi!
> 
> the foreign key problem seems to come from using an incorrect schema 
> name. ie. in a database i am using i have a few schemas. i am working on 
> one of them and when selecting a referencing table all table names are 
> displayed as 'schema.tablename' except the tables from the current 
> schema i'm working on, where just the form 'tablename' is used. and 
> pgadmin3 appears to use the public schema if no schema seems to be 
> specified, which then returns no columns.
> 
> ie: i am working on a schema called 'myschema' and i select a table 
> 'tablename' as a referenced table. pgadmin generates the following query 
> to retrieve the column names from a newly selected table:
> SELECT attname
>           FROM pg_attribute att, pg_class cl, pg_namespace nsp
>          WHERE attrelid=cl.oid AND relnamespace=nsp.oid
>            AND nspname='public'
>            AND relname='tablename'
>            AND attnum > 0
> 
>          ORDER BY attnum
> 
> instead of
> SELECT attname
>           FROM pg_attribute att, pg_class cl, pg_namespace nsp
>          WHERE attrelid=cl.oid AND relnamespace=nsp.oid
>            AND nspname='myschema'
>            AND relname='tablename'
>            AND attnum > 0
> 
>          ORDER BY attnum
> 
> regards,
> Miha
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
> 

Sune B. Woeller wrote:

> Hi list,
>
> I can reproduce this error - could it be added as an
> official bug, please?


On my list for investigation.

Regards,
Andreas