From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Nikhil S <nixmisc(at)gmail(dot)com> |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: pgAdmin III: system schemas under incorrect hiearchy in EDBAS PostgreSQL mode |
Date: | 2011-02-28 13:36:57 |
Message-ID: | AANLkTikQwwhWUVpm-ga6SF5TpdD+xo-hhwc-RRqWaVRR@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Thanks - applied (with a minor tweak to make it work) :-p
On Fri, Feb 25, 2011 at 3:05 PM, Nikhil S <nixmisc(at)gmail(dot)com> wrote:
> Hi,
>
> If we use pgadmin III to browse a PPAS database that was installed in
> Postgresql mode, the "sys" and "dbo" system schemas appear incorrectly under
> the normal user "Schemas" hierarchy. The issue is occurring because the
> current sql in pgSchemaBaseFactory::CreateObjects() which tries to avoid
> showing non-system schemas is incorrect.
>
> Since these schemas are added at initdb time, IMO just checking for these
> schemas by name should be enough. This patch does just the same.
>
> Regards,
> Nikhils
>
>
> --
> Sent via pgadmin-hackers mailing list (pgadmin-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgadmin-hackers
>
>
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Nikhil S | 2011-02-28 13:49:51 | Re: pgAdmin III: system schemas under incorrect hiearchy in EDBAS PostgreSQL mode |
Previous Message | Dave Page | 2011-02-28 13:36:50 | pgAdmin III commit: Correctly identify the sys and dbo catalogs on PPAS |