Обсуждение: Hiding built-in functions
Hi, I remember at one time when I opened the functions node of the public shema for a database, it was empty, save for the function I added to the system. At this time I am seeing a list of included functions from template1 or something in addition to ones I add. Is there a way to hide the built-in functions so you can only see and work on your own set of functions? This would be a nice touch. Is there some other way to achieve this, by creating the database differently? Any insight most appreciated!! Dave
> -----Original Message----- > From: pgadmin-support-owner@postgresql.org > [mailto:pgadmin-support-owner@postgresql.org] On Behalf Of Dave Lazar > Sent: 28 February 2005 17:38 > To: pgadmin-support@postgresql.org > Subject: [pgadmin-support] Hiding built-in functions > > Hi, > > I remember at one time when I opened the functions node of the public > shema for a database, it was empty, save for the function I added to > the system. > > At this time I am seeing a list of included functions from template1 > or something in addition to ones I add. > > Is there a way to hide the built-in functions so you can only see and > work on your own set of functions? > > This would be a nice touch. Is there some other way to achieve this, > by creating the database differently? No, unfortunately there is no way to tell what is yours and what came from template1. The best solution is to just try to use different schemas to segregate things. Regards, Dave.
It would be nice to have thse broken out or sperated into user and system functions or for pgAdminIII to allow you to create organisational folders within its tree view. I have resorted to naming all my functions zzfunc_xxx to keep them all together at the end of the list.. Oisin ----- Original Message ----- From: "Dave Page" <dpage@vale-housing.co.uk> To: "Dave Lazar" <hunkybill@gmail.com>; <pgadmin-support@postgresql.org> Sent: Monday, February 28, 2005 3:59 PM Subject: Re: [pgadmin-support] Hiding built-in functions > > >> -----Original Message----- >> From: pgadmin-support-owner@postgresql.org >> [mailto:pgadmin-support-owner@postgresql.org] On Behalf Of Dave Lazar >> Sent: 28 February 2005 17:38 >> To: pgadmin-support@postgresql.org >> Subject: [pgadmin-support] Hiding built-in functions >> >> Hi, >> >> I remember at one time when I opened the functions node of the public >> shema for a database, it was empty, save for the function I added to >> the system. >> >> At this time I am seeing a list of included functions from template1 >> or something in addition to ones I add. >> >> Is there a way to hide the built-in functions so you can only see and >> work on your own set of functions? >> >> This would be a nice touch. Is there some other way to achieve this, >> by creating the database differently? > > No, unfortunately there is no way to tell what is yours and what came > from template1. The best solution is to just try to use different > schemas to segregate things. > > Regards, Dave. > > ---------------------------(end of broadcast)--------------------------- > TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org > > > > -- > No virus found in this incoming message. > Checked by AVG Anti-Virus. > Version: 7.0.306 / Virus Database: 266.5.2 - Release Date: 2/28/2005 > >
> -----Original Message----- > From: Oisin Glynn [mailto:me@oisinglynn.com] > Sent: 01 March 2005 02:35 > To: Dave Page; Dave Lazar; pgadmin-support@postgresql.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