Explorer doesn't show overloading

[Dwayne]

Hi there,

Not sure if this is considered a bug or not, since it likely depends on how you use the tree.

I personally find it misleading (when using the tree on the left to browse through code) that it doesn't show when a package function or procedure is overloaded. Yes, if you right-click-> Test or something like that it *does* ask you to choose which overloaded version you want to test, but I'd like to see the fact that there are multiple signatures in the tree.

We have a few users that use PLSQL Developer mainly to browse the database, and to see and API view of the code that I've written for the team, and not showing all versions of the proc/function is misleading.

Granted they should be using the API documentation I've provided, which does detail this, but having them able to see it in the tool in which they work would help.

Anyone else vote for this?

 

[Claus Pedersen]

Hi Dwayne,

I agree with you on this. Since the tree also shows parameters, all overloads for a method should be displayed, or at least have an indicator showing that overloads exist, (*) after filename, or similar.

Personally, I mostly use the object browser to point at a package to view or a method to test and in that case, the test window will show a pop-up to let the me select an overload.

 

[Bernhard S]

I agree with the previous posts.
In addition I don't like the way overloaded functions/procedures are shown in command window describe either. I have a package with two function, one with one number parameter, the other with two number parameters. It's shown in command window like this:

SQL> desc pkg_bsa_test.my_func1
Parameter Type   Mode Default?
--------- ------ ---- --------
(RESULT)  NUMBER
P_NUM1    NUMBER IN
(RESULT)  NUMBER
P_NUM1    NUMBER IN
P_NUM2    NUMBER IN

SQL>

This makes it hard to tell what each function looks like and that we're dealing here with overloaded functions.
If I decribe the whole package, there's no indication that the function exists in overloaded variants:

SQL> desc pkg_bsa_test
Element  Type
-------- --------
MY_FUNC1 FUNCTION

I think SQL*Plus does this a lot better and command window should adapt to that:

SQL> desc pkg_bsa_test
FUNCTION MY_FUNC1 RETURNS NUMBER
 Argument Name                  Typ                     In/Out Defaultwert?
 ------------------------------ ----------------------- ------ --------
 P_NUM1                         NUMBER                  IN
FUNCTION MY_FUNC1 RETURNS NUMBER
 Argument Name                  Typ                     In/Out Defaultwert?
 ------------------------------ ----------------------- ------ --------
 P_NUM1                         NUMBER                  IN
 P_NUM2                         NUMBER                  IN

SQL>

Command window should do it more similar.
If I do a describe using right-click on

pkg_bsa_test.my_func1

I can switch through the different overloaded version using arrows. This makes it more clear that we're dealing with overloaded functions here.