I hesitated to post my idea here because I did not want to seem ungrateful (as if the feature were not good enough).
One of the ways that it saves time for me is when I copy a SQL statement to the SQL Editor in order to test it. In the past, I had to replace the placeholders with actual data in order to run the query. Once I had the query running correctly, I had to replace the data with the placeholders before copying it back to the source code. This feature allows me to leave the placeholders in the SQL statement. It also allows me to run a query multiple times with different parameter values more easily.
It turns out that I actually have two ideas related to this.
1. Expand the feature to recognize parameters in stored procedures.
For example, if sp1 is defined as:
create or replace procedure sp1
(
p_parm1 string, -- This is parameter 1
p_parm2 int -- This is parameter 2
)
...
then p_parm1 and p_parm2 would appear in the parameter panel.
There could be multiple calls to parameterized stored procedures(/functions) within a BEGIN...END block. If the Editor could distinguish between them and show the parameters for the call at the cursor location, that would be a nice feature.
2. Auto-fill of parameters in stored procedures
This would allow a procedure call to be typed as:
call sp1()
in the SQL Editor. A menu option/shortcut key would cause the statement to be replaced with
call sp1
(
p_parm1 string, -- This is parameter 1
p_parm2 int -- This is parameter 2
)
The Editor would need to recognize that the stored procedure has parameters and would replace the () with the text from the stored procedure itself. This would retain any formatting (tab, return) that the developer included so that the result would be according to the developer's preference. Also, this operation would apply only to calls followed by "()" that target a stored procedure with parameters.
There could also be a setting in Preferences to allow this to happen automatically whenever a call to a parameterized procedure is followed by ().