Comments
Sort by recent activity
In my case, it has nothing to do with the select query. I understand that SQL prompt has issues parsing some certain queries and formats, and I usually know how to "workaround" these by changing the structure of my query.
In my case, it is simply forgetting tables and columns. I can even clear my query window, write a simple "select * from TableName", and the table won't even come up in the list (even though almost all other tables do show up). I can then do a "Refresh Cache", and it will then show up in the candidates list. This workaround fixes the issue 100% of the time, and this happens often with my colleagues as well, so it's not just me. / comments
In my case, it has nothing to do with the select query. I understand that SQL prompt has issues parsing some certain queries and formats, and I usually know how to "workaround" these by changing t...
Any updates on this? We're still having the issue.
If there's anyway I can help troubleshoot, let me know. For example, if it would help to send you a cache file before (when the members are missing) and after (when I do a refresh and restore them), let me know.
Thanks. / comments
Any updates on this? We're still having the issue.
If there's anyway I can help troubleshoot, let me know. For example, if it would help to send you a cache file before (when the members are miss...
That's interesting. I asked the same question prior to the release (I was considering a pre-order), because I wanted to use it for both professional and personal use. I was told that I *could* in fact install on both with one license. Actually, I was told up to three activations.
I still have the email where I asked the question and received this response. There was no indication that this was a "special offer" either. / comments
That's interesting. I asked the same question prior to the release (I was considering a pre-order), because I wanted to use it for both professional and personal use. I was told that I *could* in...
Same here. I have not yet purchased a license, but I was not aware that the beta would expire. / comments
Same here. I have not yet purchased a license, but I was not aware that the beta would expire.
I agree. I also posted this same suggestion on this thread. / comments
I agree. I also posted this same suggestion on this thread.
Additionally, in VS, <ctrl+page up> and <ctrl+page down> are used to go to the top and bottom of the list, so maybe SQL Prompt can adopt these shortcuts. / comments
Additionally, in VS, <ctrl+page up> and <ctrl+page down> are used to go to the top and bottom of the list, so maybe SQL Prompt can adopt these shortcuts.
One other suggestion.
Have an option to only pop up the candidate list if there are no characters behind the cursor. For example, if I hit <tab> when the cursor is in front of a column name, I don't want the candidate list to pop up. I may rarely need to see the candidate list when doing this, but I would just use <ctrl+space> in these situations.
This is mainly a problem when restructuring poorly structured queries to make them more readable, and using <space> and <tab> both constantly pop the candidate list up.
I beleive this would make it more consistent w/ VS behavior.
Thanks. / comments
One other suggestion.
Have an option to only pop up the candidate list if there are no characters behind the cursor. For example, if I hit <tab> when the cursor is in front of a column name, I don...