Re: PL/SQL: dynamically determining parameter names and values

In article <newscache$co2o8j$05j$1_at_news.liwest.at>, CN says...

>
> Hi!
>
> PL/SQL is rather poor on reflection but it is not totally impossible.
> This is the direction I would take if I really had to do that:
>
> - Define a schema-level trigger that executes 'after create'.
> - If ora_dict_obj_type is some PL/SQL then load the code from user_source
> into some pl/sql table.
> - Query user_arguments for every included top-level procedure/function and
> insert tracing code into the table at the appropriate places (you will
> have to write a simple parser or insert place-holders where the log info
> should go).
> - Re-execute the code in the pl/sql table (make sure that the trigger
> doesn't start a cycle).
>
> Lucas Jellema of AMIS wrote about AOP a few months ago, this is more
> generic: http://technology.amis.nl/blog/?p=1083
>

Thanks Chris.

Not a straightforward proposition then!

-- 
jeremy