Hi there,
First of all, on behalf of myself and the other guys in our development team, what a great product. -Well done. Looking forward to V3.
Below are some things that we found in SQLPrompt v2.
Bugs & Design dislikes:
===============
(1). When testing auto insert snippets, if you use the {TAB} character, then click "test snippet", it will enter an infinite loop. The first time this happened I let it go for <10 sec and the OS rebooted itself.
(2). When testing auto insert snippets, the test output area seems to put in extra CRLF's. This makes it a little bit less friendly when you are trying to test snippets that position the cursor after outputting the desired text.
(3). When typing SQL, using TAB to format your code causes an unwanted appearance from the intellisence prompt. Maybe there could be an option not to show the candidate list when there is text immediately after the cursor?
(4). Some of the guys noted that when typing an "INSERT INTO X SELECT FROM Y" type query that the candidate list doesn't show a list of available tables in addition to the fields from the insert table.
Suggestions & Feature requests:
=====================
(5). An option to maintain the indentation level when executing an auto insert would be nice. I often insert mulit-line snippets, the first line of which is indented correctly, but the subsequent lines require formatting.
(6). It would be nice to have the variables that you declared earlier in the stored proc you are writing available in the candidate list. I was thinking that maybe by highlighting the variable and registering it with SQLPrompt (via a specific hot key combination for example) might be an easy way to implement it until a better alternative is available?
(7). Currently you can use "* <TAB>" to output all fields. Nice feature. It is annoying to have to format them after this though. My thought was that something like "*F <TAB>" could be used to output all fields again, but with user configured formatting. Some formating options might include: "Maintain indentation level on each new line", "CRLF after each field", "Insert this text after last field is output: xxxx", "Pre-pend each field with @ . ..... Maybe even *F1 <TAB>" - Formatting preset 1, "*F2 <TAB>" formatting preset 2" ...etc...
(8). Often I find myself typing a query that ends with "WHERE CustomerID = @CustomerID" or something similar. If SQLPrompt kept it's eye out for "WHERE fieldName = ", then it could add to it's list of candidates the exact field that is being compared but pre-pended with @.
(9). Sometimes I come across database tables with fields that are also SQL keywords. It would be good if SQL Prompt recognised the fields in a table that were also keywords and automatically inserted them from the candidate list pre-wrapped in [].
That's it for now. Looking forward to reading your comments. By the way we have some beta testers here for v3 if you're still looking!
Keep up the great work guys it's looking really good.
Regards,
Dozman
Operating system(s): Win 2k Pro (sp4), Win XP Pro (sp2)
First of all, on behalf of myself and the other guys in our development team, what a great product. -Well done. Looking forward to V3.
Below are some things that we found in SQLPrompt v2.
Bugs & Design dislikes:
===============
(1). When testing auto insert snippets, if you use the {TAB} character, then click "test snippet", it will enter an infinite loop. The first time this happened I let it go for <10 sec and the OS rebooted itself.
(2). When testing auto insert snippets, the test output area seems to put in extra CRLF's. This makes it a little bit less friendly when you are trying to test snippets that position the cursor after outputting the desired text.
(3). When typing SQL, using TAB to format your code causes an unwanted appearance from the intellisence prompt. Maybe there could be an option not to show the candidate list when there is text immediately after the cursor?
(4). Some of the guys noted that when typing an "INSERT INTO X SELECT FROM Y" type query that the candidate list doesn't show a list of available tables in addition to the fields from the insert table.
Suggestions & Feature requests:
=====================
(5). An option to maintain the indentation level when executing an auto insert would be nice. I often insert mulit-line snippets, the first line of which is indented correctly, but the subsequent lines require formatting.
(6). It would be nice to have the variables that you declared earlier in the stored proc you are writing available in the candidate list. I was thinking that maybe by highlighting the variable and registering it with SQLPrompt (via a specific hot key combination for example) might be an easy way to implement it until a better alternative is available?
(7). Currently you can use "* <TAB>" to output all fields. Nice feature. It is annoying to have to format them after this though. My thought was that something like "*F <TAB>" could be used to output all fields again, but with user configured formatting. Some formating options might include: "Maintain indentation level on each new line", "CRLF after each field", "Insert this text after last field is output: xxxx", "Pre-pend each field with @ . ..... Maybe even *F1 <TAB>" - Formatting preset 1, "*F2 <TAB>" formatting preset 2" ...etc...
(8). Often I find myself typing a query that ends with "WHERE CustomerID = @CustomerID" or something similar. If SQLPrompt kept it's eye out for "WHERE fieldName = ", then it could add to it's list of candidates the exact field that is being compared but pre-pended with @.
(9). Sometimes I come across database tables with fields that are also SQL keywords. It would be good if SQL Prompt recognised the fields in a table that were also keywords and automatically inserted them from the candidate list pre-wrapped in [].
That's it for now. Looking forward to reading your comments. By the way we have some beta testers here for v3 if you're still looking!
Keep up the great work guys it's looking really good.
Regards,
Dozman