From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Jochem van Dieten" <jochemd(at)oli(dot)tudelft(dot)nl> |
Cc: | <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: altering the name of the public schema [SOLVED] |
Date: | 2002-12-02 09:57:12 |
Message-ID: | 03AF4E498C591348A42FC93DEA9661B8128CCC@mail.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
> -----Original Message-----
> From: Jochem van Dieten [mailto:jochemd(at)oli(dot)tudelft(dot)nl]
> Sent: 02 December 2002 09:56
> To: Dave Page
> Cc: pgadmin-support(at)postgresql(dot)org
> Subject: Re: [pgadmin-support] altering the name of the
> public schema [SOLVED]
>
>
> Dave Page wrote:
> 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)?
Problem is, there is no guarantee that that oid won't change in the
future - it's for that reason that we don't ever assume an OID value in
pgAdmin.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Macropac | 2002-12-02 11:41:39 | unsubscribe |
Previous Message | Jochem van Dieten | 2002-12-02 09:55:32 | Re: altering the name of the public schema [SOLVED] |