Settings and activity
31 results found
-
1 vote
Doug
shared this idea
·
-
2 votesDoug
shared this idea
·
-
14 votesDoug
supported this idea
·
-
18 votesDoug
supported this idea
·
-
4 votesDoug
supported this idea
·
-
4 votesDoug
shared this idea
·
-
3 votesDoug
supported this idea
·
-
9 votesDoug
supported this idea
·
-
2 votes
An error occurred while saving the comment -
2 votesDoug
shared this idea
·
-
344 votes
An error occurred while saving the comment Doug
commented
I know there are a lot of suggesting covering a lot of topics, but the community asks about the status of a suggestion more than once, and two+ years go by without any response from Redgate, you have to wonder if they are even reading these or care about our feedback.
Is this going to be implemented at some point in the future? Is it under consideration? It was first posted over 6 years ago. It has over 300 votes. I would think that would deserve some kind of comment from Redgate.An error occurred while saving the comment Doug
commented
Me too.
-
52 votesDoug
supported this idea
·
-
3 votesDoug
shared this idea
·
-
22 votesDoug
supported this idea
·
An error occurred while saving the comment Doug
commented
Find Next and Prev.
-
6 votesDoug
supported this idea
·
-
2 votes
An error occurred while saving the comment Doug
commented
Optionally, allow a "Goto Definition" option in the popup if the value of the variable has been set in code, as well as a "Return to Previous Location" option. Since the tooltip shows the actual declaration (e.g. "local variable @MyVar DATE") I would expect this action to take me to the previous location where the variable was set to a value, either through a SET or SELECT. "Return to Previous Location" would return me to the point prior to jumping to the definition.
Thus, if I am on line 817 that has WHERE col = @MyVar, and I goto the definition of @MyVar, which is on line 63, "Return to Previous Location" would return me to line 817.
Goto Definition is a function of many other IDEs.An error occurred while saving the comment Doug
commented
Hans,
I don't see an issue. I'm saying, if it can be determined, show it. If, at the top of my code, I state DECLARE @MyVar INT = 123; then don't set it to anything else anywhere in code, then the value is 123. I don't see how this differs any more than being able to show me unused variables.
The last known value obviously would not be known if I state DECLARE @MyVar INT = (SELECT value FROM table WHERE filter = 'MyVar') and I would not expect SQL Prompt to run the code to determine the value (it would be nice :-)), but a lot of times variables are set at the start of code with the intent of functioning more like constants and if a scan of code can determine the last known value (just like a scan of code can determine unused variables, or even a variable type to display) then capturing the value it was set to should not be an issue. The code is not being executed, just scanned.
Doug
shared this idea
·
-
76 votes
Thanks for all the feedback on this suggestion. The team will take the item under review and we’ll update here with next steps.
Doug
supported this idea
·
-
2 votes
An error occurred while saving the comment Doug
commented
Plus allowing users to set colors would help those of us who are color-blind and the default schema doesn't work for us.
Doug
supported this idea
·
-
16 votesDoug
shared this idea
·
-
4 votesDoug
shared this idea
·
I'd rather convert CASE to IIF() :-)