| From: | Jochem van Dieten <jochemd(at)oli(dot)tudelft(dot)nl> |
|---|---|
| To: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
| Cc: | pgadmin-support(at)postgresql(dot)org |
| Subject: | Re: altering the name of the public schema [SOLVED] |
| Date: | 2002-12-02 09:55:32 |
| Message-ID: | 3DEB2E14.1070503@oli.tudelft.nl |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
Dave Page wrote:
> From: Jochem van Dieten [mailto:jochemd(at)oli(dot)tudelft(dot)nl]
>
>>Could it be that somewhere in pgAdminII there is a reference to the OID
>>2200 that is assigned to the public schema by default?
>
>
> pgAdmin hides system objects by default, but in the case of the public
> schema it makes an exception bcause hiding public would not be sensible.
> It does it by a combination of name and OID: the oid is less than the
> last system oid, so it is hidden, except if it is called public.
>
> Switch on show System Objects on the view menu and you should see it.
That indeed solves this issue. May I make an enhancement request that
objects with an OID less than the last system OID are hidden, unless the
OID is 2200 (system OID's are not cycled, are they)?
Jochem
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2002-12-02 09:57:12 | Re: altering the name of the public schema [SOLVED] |
| Previous Message | Dave Page | 2002-12-02 09:10:52 | Re: 32 Character Constraint Name Bug? |