Comments
Sort by recent activity
I went ahead and did that, but I really don't like using that as a method for suggesting features and reporting bugs. The biggest reason is that you are really limited to posting 10 suggestions since you have to have votes available to post a new one. (I had to take a vote away from something else.) / comments
I went ahead and did that, but I really don't like using that as a method for suggesting features and reporting bugs. The biggest reason is that you are really limited to posting 10 suggestions sin...
Anu Deshpande wrote:
It starts suggesting the column names as till then the query is not valid.
Really, can you point me to the point in the batch that is invalid? (Adding the comma actually makes it invalid until you add a valid field name.) The batch that I posted is valid and runs fine for me as long as you take the <CURSOR> placeholder out.
It should suggest C_ID and show the other information. For example type your comma, then delete your comma and hit CTRL-space, suggestions will come up, and yet the query is exactly how it was when you pasted it. Why does it act differently after typing than after pasting or opening a file. / comments
Anu Deshpande wrote:
It starts suggesting the column names as till then the query is not valid.
Really, can you point me to the point in the batch that is invalid? (Adding the comma actually m...
Anu,
I'm not asking for a feature to turn indentation off, I'm asking for a bug to be fixed. I assume what is happening is that the TAB key stroke is being interpreted once to indent, and one to expand the *.
Or are you saying that it is indenting a level when it expands on purpose? (It never did that in SQL Prompt 3, and SQL Prompt 4 was broken, it got the first column correct, and indented the remaining columns.) / comments
Anu,
I'm not asking for a feature to turn indentation off, I'm asking for a bug to be fixed. I assume what is happening is that the TAB key stroke is being interpreted once to indent, and one to ex...
Is there any plans to fix the problem of * expansion indenting an extra level? (It is great that the new 5.2.8.2 version can use tabs, but it is still a pain to have to select the columns that are added and then un-indent them.)
This has been logged under various SP numbers: SP-2796/2838/3808. / comments
Is there any plans to fix the problem of * expansion indenting an extra level? (It is great that the new 5.2.8.2 version can use tabs, but it is still a pain to have to select the columns that are ...
I too have noticed this, and have sent an email requesting the fixed version. / comments
I too have noticed this, and have sent an email requesting the fixed version.
I agree it is definitely more of a pain than it is worth. / comments
I agree it is definitely more of a pain than it is worth.
I have noticed the same thing, I have a space after the FROM in my SSF snippet as well, and then have to hit ctrl-space to get suggestions. It would be nice if it brought the list up automatically.
I'm thinking maybe an additional placeholder like $SUGGEST$ to let it know that we want the suggestions to come up at that point. ($SUGGEST$ would probably need to position the cursor as well.) / comments
I have noticed the same thing, I have a space after the FROM in my SSF snippet as well, and then have to hit ctrl-space to get suggestions. It would be nice if it brought the list up automatically....
I have added the $SUGGEST$ placeholder feature request to the uservoice site, so if you like the idea you should go vote for it: http://redgate.uservoice.com/forums/94413-sql-prompt-feature-suggestions/suggestions/1519439-add-suggest-placeholder-in-snippets / comments
I have added the $SUGGEST$ placeholder feature request to the uservoice site, so if you like the idea you should go vote for it: http://redgate.uservoice.com/forums/94413-sql-prompt-feature-suggest...
I agree that this needs to be fixed, even if it is a simple option that you check that removes these keywords from being capitalized anywhere. (I would rather have them not change case where they can be upper case than have it change it and break the code.) / comments
I agree that this needs to be fixed, even if it is a simple option that you check that removes these keywords from being capitalized anywhere. (I would rather have them not change case where they c...
Paul,
Any update from the developers as to what the issue might be? (Is it a particular feature like CTEs?) / comments
Paul,
Any update from the developers as to what the issue might be? (Is it a particular feature like CTEs?)