Re: SQL Function call tree

From: Niall Litchfield <n-litchfield_at_audit-commission.gov.uk>
Date: Wed, 13 Feb 2002 16:05:14 -0000
Message-ID: <3c6a8ec0$0$8510$ed9e5944_at_reading.news.pipex.net>


ah that makes sense now. Unfortunately I have never seen a utility that would do this. The optomistic among us would say that that was what the documentation was for. Unfortunatley we all know the general standard of documentation.

--
Niall Litchfield
Oracle DBA
Audit Commission UK
*****************************************
Please include version and platform
and SQL where applicable
It makes life easier and increases the
likelihood of a good answer

******************************************
"DW" <david.wilkie_at_gecapital.com> wrote in message
news:92b9b544.0202130111.62fcc115_at_posting.google.com...

> "Niall Litchfield" <n-litchfield_at_audit-commission.gov.uk> wrote in message
news:<3c69248b$0$233$ed9e5944_at_reading.news.pipex.net>...
> > if you mean a PL/SQL package what would such a utility give you that
DESC
> > doesn't.
> >
>
> It would give you an idea of what functions call what. Here is an
> example of the output from MetreTree (a UNIX utility which does this
> for C progs) ...
>
> main
> +---print_error
> | +---print_warning
> | | `---strip_path
> | +---strip_path
> | `---sqlglm
> +---print_warning
> +---strip_path
> `---sqlglm
>
> As you can see from this, "main" calls two functions - "print_error" &
> "print_warning". Each of these functions are also detailed into what
> they call. This would be very useful when trying to identify the
> entry points into a package.
>
> Is this any clearer ?
>
> Regards,
> David.
Received on Wed Feb 13 2002 - 17:05:14 CET

Original text of this message