Comments
Sort by recent activity
Many of these anoyances/defects you identified were reported in the in the first few days of the Beta. The answer at that time was that they would incorporate the feedback into the final product.
Regarding the timebomb stuff, there was an item in the release notes that said the beta would expire on the 17th. See http://www.red-gate.com/MessageBoard/viewtopic.php?t=3358 for details and beta wrap-up info.
They've said they will release the final to the beta testers when its available, but no word yet on if there will be a trial edition. / comments
Many of these anoyances/defects you identified were reported in the in the first few days of the Beta. The answer at that time was that they would incorporate the feedback into the final product.
...
Tilman wrote:
There probably won't be another beta release. So uninstalling is your only option.
Will there be some opportunity to try SQL Prompt 3?
Due to reported defects (intellisense that did not repect the context; tab insertion; alias issues) and beta limitations (no SSF snipet) I found SQL Prompt 2 (even with its quirks) helped me get my job done easier. Before I purchase SQLP3 I need to see the defects corrected and the usability improved. / comments
Tilman wrote:
There probably won't be another beta release. So uninstalling is your only option.
Will there be some opportunity to try SQL Prompt 3?
Due to reported defects (intellisense that ...
Tilman wrote:
I did not alias MyTable; however, the insertion of MyTableID included an alias:
What were the options settings when you encountered this? Did you manually remove the alias from MyTable? It's of course still a bug, i just need to be sure i'm reproducing it correctly.
I am able to reproduce it. I did not remove the alias since I had typed the entire table name. I used SQLP3 only for column name in the where clause, to which it added an alias.
Options I have checked are:
Assign aliases to tables and views
Qualify non-aliases columns with table or view name
Auto-popup candidate list
All Completion Keys / comments
Tilman wrote:
I did not alias MyTable; however, the insertion of MyTableID included an alias:
What were the options settings when you encountered this? Did you manually remove the alias fro...
I used "ATA" in my example because "SSF" in nowhere to be found.
Is this a defect or part of the beta that the candidates for snippets only contains up to "cuni"?
Thanks for the usage tip; I'm conditioned by how I use Visual Studio and I've always considered intellisense a completion tool "<type something>, now complete it" as opposed to "I want to complete what I type next, <type something>". / comments
I used "ATA" in my example because "SSF" in nowhere to be found.
Is this a defect or part of the beta that the candidates for snippets only contains up to "cuni"?
Thanks for the usage tip; I'm cond...
There are no snippets that start with s. Where is the "select * from " snippet? The list only contains "acud" down to "cuni".
For the snippets to be efficient, the key combos necessary to generate them need to be much shorter than the text themselves.
SQLP2's "ssf" was efficient.
The SQLP3 key combos appear to be less efficient:
"ata" [crtl] + [space] + [crtl] + [R arrow] + [enter] / comments
There are no snippets that start with s. Where is the "select * from " snippet? The list only contains "acud" down to "cuni".
For the snippets to be efficient, the key combos necessary to generat...
I have observed this behavior as well; after pressing tab for completion the tab is written to the end of the intellisense'd text:
typed:
select * from Autho + [tab]
got:
select * from Authors <tab> / comments
I have observed this behavior as well; after pressing tab for completion the tab is written to the end of the intellisense'd text:
typed:
select * from Autho + [tab]
got:
select * from Authors <tab>
Bart Read wrote:
For example:
EXEC sp_helptext @objname:='sp_help', @columnname:=NULL
An option to insert a complete stored procedure invocation signature will be available in the final release.
Great! I came to the forum to suggest it. Will this include the ability to configure parms to appear on a separate lines? If you have many inputs I'd prefer to see it formatted:
EXEC sp_helptext
@objname:='sp_help',
@columnname:=NULL
/ comments
Bart Read wrote:
For example:
EXEC sp_helptext @objname:='sp_help', @columnname:=NULL
An option to insert a complete stored procedure invocation signature will be available in the final rel...
I'd like to have control over the formatting of the alias. Our coding standard, (like it or not), is to not use the AS when creating the alias, so having the ability to not generate the AS would be a feature for our team.
About how intellisense works...
It would be better usability if given I have the DOT option checked in the ]SQL Prompt 3 options that when I type the following:
select *
from Authors a
where a.
The dot on the last line should produce intellisense of columns for that aliased table. It is not doing that in 3.0.0.300 / comments
I'd like to have control over the formatting of the alias. Our coding standard, (like it or not), is to not use the AS when creating the alias, so having the ability to not generate the AS would b...
Bart Read wrote:
* Do you like the ability to filter the candidates by type? (CTRL plus LEFT ARROW or RIGHT ARROW)
Until I read this post it wasn't obvious to use ctrl arrow. It appeared you had to use the mouse. How about adding hover text for the first x usages that says "To select a candidate group use the [crtl] + [arrow]"
* Is it the right size to start off with?
Sure, but being able to resize is wonderful. How about ability to set the font size?
* Does it work the way you think it should?
Not yet. I may have to change my thinking. / comments
Bart Read wrote:
* Do you like the ability to filter the candidates by type? (CTRL plus LEFT ARROW or RIGHT ARROW)
Until I read this post it wasn't obvious to use ctrl arrow. It appeared you ...