Activity overview
Latest activity by labreuer
I checked off "Include system objects in the candidate list" and I got no intellisense after typing "INFORMATION_SCHEMA.", nor did I get intellisense for the columns in the INFORMATION_SCHEMA.COLUMNS view. The checked state of "Show objects for specified owner or schema" did not appear to affect anything. If I am in the master database, where the INFORMATION_SCHEMA views are defined, I do get intellisense after typing "INFORMATION_SCHEMA.", but not for the columns.
Choosing the "force lowercase" object appears to solve part of the issue. However, this does not fix the "USER( database)" problem I mentioned above. I determined that this is because 3.0's intellisense does not prefer exact matches. In other words, if I type "use" and that is in the intellisense list, intellisense should accept it instead of suggesting an item before it, like "USER". I should still be able to navigate the list up and down and choose something other than "use", but it should be the default. (If you disagree, I would like to hear your reasoning.) / comments
I checked off "Include system objects in the candidate list" and I got no intellisense after typing "INFORMATION_SCHEMA.", nor did I get intellisense for the columns in the INFORMATION_SCHEMA.COLUM...
Disabling functionality & Capitalization
Is it possible to disable the "Other candidates" category? I set the popup delay to 50ms so that I could have shortcuts expand without pressing ctrl-space, but that has caused SQL Prompt to capita...