Re: Dropping wrong object - Mailing list pgadmin-support

From Cheetah
Subject Re: Dropping wrong object
Date
Msg-id a9d6776b050128071024cebd50@mail.gmail.com
Whole thread Raw
In response to Re: Dropping wrong object  (Andreas Pflug <pgadmin@pse-consulting.de>)
List pgadmin-support
On Fri, 28 Jan 2005 13:45:02 +0000, Andreas Pflug
<pgadmin@pse-consulting.de> wrote:
> I hate search_path....

Well, on average it's been quite useful for me, but that's neither
here nor there.

> I think we should add an option to suppress the public. prefix if
> desired. This may be on by default if no $user (or other schema
> preceding public in search_path) exists.
> It's in BUGS.txt now.

Sorry if I'm misunderstanding something, but it seems that the
solution is to *always* put in the schema prefix, unless the server is
an old enough version that it doesn't support schema.  The suppression
of the public. prefix is what's causing the problem I experienced.

--    -- Cheetah


pgadmin-support by date:

Previous
From: Andreas Pflug
Date:
Subject: Re: pg_dump from pgadmin and Postgres 8.0
Next
From: "Keith Worthington"
Date:
Subject: Re: "http://pgadmin.org/" <> www.pgadmin.org