Foreign Key selection / no public schema

From: Philipp Specht <phlybye(at)gmx(dot)net>
To: pgadmin-support(at)postgresql(dot)org
Subject: Foreign Key selection / no public schema
Date: 2007-01-20 12:33:02
Message-ID: 45B20BFE.10308@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

Hi!

I hope you can tell me how to avoid the following problem:

I'm using pgadmin 1.6.2 on MacOSX (same problem with 1.6.1) connecting
to a 8.2.0 database.

I've renamed my public schema and created a new schema. There's no
'public' schema any more.

Now pgadmin can't find the columns of a referenced table to populate the
drop down selector.

After activating debug logging I found that pgadmin tries to find the
columns in the "public" schema.

###
2007-01-20 13:03:35 QUERY : Set query (xxx:5432): 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='xxx'
AND attnum > 0

ORDER BY attnum

###

'search_path' for the logged in user is set to the names of my new schemas.

That's a bug? A missing feature? Or did I miss a configuration parameter?

Thanks for your help,
Philipp

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Dave Page 2007-01-22 11:47:28 Re: Foreign Key selection / no public schema
Previous Message Dave Page 2007-01-19 17:56:17 Re: Re : Copy from Edit data, Paste into OpenOffice