On Tue, Sep 30, 2008 at 2:19 AM, Robins Tharakan <tharakan(at)gmail(dot)com> wrote:
> While making a complex database back-end, I have at-hand about 200 odd
> functions and frankly 'management of functions' is already getting quite
> tedious. Since the count is certain to rise, I am looking for a good tool to
> do this.
> By management, I guess I am looking at some kind of tagging mechanism, where
> it could keep stored a list of tags for each function (tags that I provide,
> for each new function created) and it be able to provide a comfortable way
> of searching/browsing through the list.
The problem IMO is that you are thinking of the database as a code
repository. It isn't...you should be thinking of it a compiler.
Strictly speaking what you are asking could be done by simply
searching pg_proc prosrc column for 'tags' you insert into code
comments in the function. I would not advise doing this.
Keep your 'create function' statements in external files and load them
form there into the database. Those files can then be checked into a
source control tool, and either organized into a directory tree or
tagged with the in-code documentation.
From there you can build exotic things like scripts that track
function dependencies if you change a core table for example.
In response to
pgsql-hackers by date
|Next:||From: Alvaro Herrera||Date: 2008-09-30 18:02:09|
|Subject: Block-level CRC checks|
|Previous:||From: Heikki Linnakangas||Date: 2008-09-30 15:22:33|
|Subject: Re: Index size increases after VACUUM FULL|
pgadmin-hackers by date
|Next:||From: svn||Date: 2008-10-01 20:02:53|
|Subject: SVN Commit by guillaume: r7488 - trunk/pgadmin3/pgadmin/dlg|
|Previous:||From: Robins Tharakan||Date: 2008-09-30 06:19:31|
|Subject: Function management in PG|