Revert "Use sys.all_objects for accurate function and procedure filtering" #2751
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reverts #2705
This change is being reverted due to differences in behavior observed between:
Specifically:
getProcedures() and getFunctions() return procedure/function names without numbered suffixes, since sys.all_objects does not expose numbered procedures.
In contrast, getProcedureColumns() and getFunctionColumns() query sp_sproc_columns, which does return numbered procedures, leading to inconsistencies across these APIs.
There was an effort done to make getProcedureColumns() and getFunctionColumns() work in PR#2743.
This PR addressed these differences, but SQL Server still supports numbered procedures, and users can benefit from grouped procedures (see here : sp_proc_columns)
To maintain compatibility and avoid unexpected discrepancies, this PR reverts #2705 and restores the original behavior.