From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Oisin Glynn" <me(at)oisinglynn(dot)com>, "Dave Lazar" <hunkybill(at)gmail(dot)com>, <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: Hiding built-in functions |
Date: | 2005-03-01 08:04:43 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E472B809@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
> -----Original Message-----
> From: Oisin Glynn [mailto:me(at)oisinglynn(dot)com]
> Sent: 01 March 2005 02:35
> To: Dave Page; Dave Lazar; pgadmin-support(at)postgresql(dot)org
> Subject: Re: [pgadmin-support] Hiding built-in functions
>
> It would be nice to have thse broken out or sperated into
> user and system
> functions
As I said, there is no was to tell the difference between a function
from a contrib module, or one created by you. The true system functions
(and other objects) are in the pg_catalog schema which is hidden away by
default.
> or for pgAdminIII to allow you to create
> organisational folders
> within its tree view.
Why not just create a separate schema for each logical part of your
system?
Regards Dave
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2005-03-01 08:07:18 | Re: Question for using PGADMIN |
Previous Message | gini | 2005-03-01 05:38:36 | Question for using PGADMIN |