From: | Vitaly Belman <vitalyb(at)gmail(dot)com> |
---|---|
To: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
Cc: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: [pgadmin-support] Schemas causing problems :( |
Date: | 2004-07-26 17:20:36 |
Message-ID: | fa96e3c604072610208ed447f@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
> Ok, here we come back to Vitaly who says this is so easy. He'll probably
> code this within a few minutes :-)
Would if I could :). Sadly I couldn't get PGAdmin to compile under my
system (especially got vexed by the wxWindows). It is a different
subject though.
Do let me know, please, if you plan to put it in some new build.
Thanks again
On Mon, 26 Jul 2004 17:51:11 +0000, Andreas Pflug
<pgadmin(at)pse-consulting(dot)de> wrote:
> Dave Page wrote:
>
> > Perhaps the search needs to be more clever though. Consider the
> > following:
> >
> > search_path: public
> > custom type: public.text
> >
> > In this case we might need to specify pg_catalog.text to get the right
> > one.
>
> This is getting a nightmare...
>
>
> >>Maybe we should invent a switch if default schema suppression is not
> >>wanted; the search path option seems useless.
> >
> >
> > Lose the switch, but resolve the correct schema each time and display
> > appropriately? Could get nasty...
>
> Ok, here we come back to Vitaly who says this is so easy. He'll probably
> code this within a few minutes :-)
>
> Regards,
> Andreas
>
--
ICQ: 1912453
AIM: VitalyB1984
MSN: tmdagent(at)hotmail(dot)com
Yahoo!: VitalyBe
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Pflug | 2004-07-26 17:51:11 | Re: [pgadmin-support] Schemas causing problems |
Previous Message | Andreas Pflug | 2004-07-26 17:09:21 | Re: [pgadmin-support] Schemas causing problems |