Thread: pgadmin option enhancement request

Hello,

I find myself needing the ability to edit a record from within an
environment where a particular
schema is at the head of " defined searchpath" ( e.g., set
searchpath=xxx01 in psql, etc.) . The reason is
that I have a trigger on the table in question that assumes a particular
search path rather than specifying an explicit schema qualification in
front of the table name.  Without that search path, the ensuing SQL
throws an error because the engine can't find the table in the default
search path that is used by pgadmin.

Please consider the ability to define a search path for the pgadmin
session as an additional option in your file:options:general section.

Thanks,
Dick Wieland

> -----Original Message-----
> From: pgadmin-hackers-owner@postgresql.org
> [mailto:pgadmin-hackers-owner@postgresql.org] On Behalf Of
> Dick Wieland
> Sent: 18 July 2006 17:06
> To: pgadmin-hackers@postgresql.org
> Subject: [pgadmin-hackers] pgadmin option enhancement request
>
> Hello,
>
> I find myself needing the ability to edit a record from within an
> environment where a particular
> schema is at the head of " defined searchpath" ( e.g., set
> searchpath=xxx01 in psql, etc.) . The reason is
> that I have a trigger on the table in question that assumes a
> particular
> search path rather than specifying an explicit schema
> qualification in
> front of the table name.  Without that search path, the ensuing SQL
> throws an error because the engine can't find the table in
> the default
> search path that is used by pgadmin.
>
> Please consider the ability to define a search path for the pgadmin
> session as an additional option in your file:options:general section.

Search path is not something that can be sensibly set in pgAdmin because
it's a per database setting, and the only database pgAdmin ever knows
about is the maintenance DB.

We only ever set it when upgrading Slony clusters though, so you might
be able to get the desired result by adding a search_path variable to
either your database or login role (user) object.

Regards, Dave.