Comments on: Limitations of PL/Scope and How to Deal with Them https://www.salvis.com/blog/2017/10/14/limitations-of-plscope-and-how-to-deal-with-them/ Database-centric development Tue, 07 Nov 2023 22:58:04 +0000 hourly 1 https://wordpress.org/?v=7.0 By: Philipp Salvisberg https://www.salvis.com/blog/2017/10/14/limitations-of-plscope-and-how-to-deal-with-them/#comment-14911 Mon, 06 Jul 2020 16:16:45 +0000 https://www.salvis.com/blog/?p=7852#comment-14911 In reply to Andrii Oseledko.

Can you please provide a simple example? There are some options with %TYPE. Thanks.

]]> By: Andrii Oseledko https://www.salvis.com/blog/2017/10/14/limitations-of-plscope-and-how-to-deal-with-them/#comment-14907 Mon, 06 Jul 2020 09:43:50 +0000 https://www.salvis.com/blog/?p=7852#comment-14907 Yes, it is possible to calculate subprogram_id and overload number over the identifiers data using window functions, then look into user/all/dba_arguments view for a resolved routine signature. But, this approach is only applicable to PACKAGE SPEC. What would you do if you need to determine full routine signature (set of param name-type pairs) in case this routine defined exclusively in PACKAGE BODY and has at least one %TYPE param?

]]> By: Philipp Salvisberg https://www.salvis.com/blog/2017/10/14/limitations-of-plscope-and-how-to-deal-with-them/#comment-14823 Wed, 24 Jun 2020 16:14:02 +0000 https://www.salvis.com/blog/?p=7852#comment-14823 In reply to Andrii Oseledko.

You find the resolved parameter type in the column data_type of user_arguments.

]]>