From: | Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr> |
---|---|
To: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: Feature requests after crash |
Date: | 2002-02-22 11:50:03 |
Message-ID: | 200202221150.g1MBo3FP010844@www1.translationforge |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Le Jeudi 21 Février 2002 23:39, Dave Page a écrit :
> Without these parsers, we will not be able to track dependencies within
> functions or views.
Why do we need parsers?
pgAdmin I had very simple queries to track dependencies (ILIKE
'%function_foo%' clause).
This suffice to build a provides clause is each object. For example, if
"function_foo" is used in "view_bar" and "function_bar":
function_foo->provides="function:function_bar;view:view_bar"
view_bar->requires="function:function_foo";
function_bar->requires="function:function_foo";
If you prefer, provides = child, requires = father.
I agree this is not as powerfull as a recursive dependency table, but this
suffice to offer 99% security to users. The purpose is not to track n-levels
of dependecies but just visualize 1 level for security reasons.
So why not implement it in pgSchema?
Cheers,
Jean-Michel
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2002-02-22 13:31:56 | Re: Feature requests after crash |
Previous Message | Jean-Michel POURE | 2002-02-22 11:37:56 | Re: Feature requests after crash |