Refactoring suggestions
I really love the refactoring features, but came across 2 things that might be addressed.
when renaming procedure variable and the same variable name is used in other SP that is called using explicit variable assignment, e.g.
EXEC dbo.otherSp @variable = @variable,
the other SP variable gets renamed as well
(e.g. rename
@variable to @newName creates
EXEC dbo.otherSp @newName = @newName
instead of
EXEC dbo.otherSp @variable = @newName)
when variable is part of an EXEC command and parameter contains assignment operator, only the variable following an assignment operator should be renamedwhen leaving table alias as it is and changing the source table for the alias
if the new table does not contain column names used throughout the procedure,
inexistent column names get underlined as expected in most cases (selects, joins on...) but not for ROW_NUMBER() OVER (PARTITION BY /ORDER BY) inside OVER block, it seems like it's a valid column name
if renaming the alias works inside this blocks, so should the intellisense when changing the source of an alias in all places the alias is used
otherwise it's great feature and thank You for it, really helps ;)
-
AdminDevart (_, Devart) commented
Hi,
Thanks for your patience!
Please note that the refactoring function renames all occurrences consistently.
"Use Aliases Consistently" function ensures that the alias is consistently and correctly applied throughout the SQL statements.
Best,
Devart Support Team