I know of some very old tickets touching this topic. Not being sure they are watched still.
For impact analysis it would be very helpful to have dependency information on views, functions and other objects that can be used by other objects.
Quite right. :-) With respect to functions, procedures, packages not only selects but any interaction to another database object. However, I did mean to exploit the databases own dependency tracking if possible. E.g. for DB2 views like CONTROLDEP, FUNCDEP, PACKAGEDEP, TRIGDEP and VIEWDEP in SYSCAT schema might be a point of information. For PostgreSQL it probably would be pg_depend.
Thanks for the clarification. Also the information regarding the dependency tracking information.
Using this would simplify the implementation.
I will add your vote for such a feature.
Just so I understand you correct.
You mean information such as