Exact word matches don't get sorted first
This is especially causing a problem for me with the FROM and ON keywords. I have several columns that start with "from", and a table that starts with "on". So, when I type
SELECT ColumnA, ColumnB FROMit has the FromAddress column at the top of the Candidate List. Once I hit space, it auto-completes my "FROM" to FromAddress, and I have to go back and change it. Similarly, with ON, when I type
SELECT * FROM Table1 JOIN Table2 ONit has the OnCall table at the top of the Candidate List, auto completes to that, and I have to go back and change it.
To me, it seems there are 2 problems with this. First, when there's something in the list that exactly matches what I've typed, that should be moved to the top of the list. For short words, especially, I'll usually have the word typed out before I even think about using auto-completion, so I don't want it to be changed to something else.
The other problem is that it doesn't seem to determine what category of candidates are most likely to be used, very well. Since I don't have a comma before the word FROM, then it seems pretty unlikely that I would be adding another column name there, and extremely likely that I would be putting FROM there, so it would make more sense for it to be at the top. The same with ON. After the second table name in the Join statement, ON is almost always the next word, so should be at the top of the list. I realize that the candidate sort ordering is somewhat subjective, but I don't think I'm in the minority at least with these examples.
I know that I can increase the Candidate List delay, so it doesn't display before I type the space after from/on. However, I type pretty fast, so I need the delay low enough that it shows up before I'm done typing longer words as well. Also, I would lose the auto-capitalization from SQL Prompt, in that case.
Don't get me wrong. Version 3 is leaps and bounds better than 2 was (I love the concept, but I couldn't even stand 2 long enough to keep it for the entire trial period). For the most part, I've loved what I've seen of it in the past 2 days, and while I do agree with some of the other request I've seen in these forums, I can live without them. However, this problem that I've listed is becoming a deal breaker for me. It's actually causing me more work, and slowing down my work-flow, because I keep having to go back and undo what SQL Prompt did.
Wow, this ended up being a long post. Sorry about that, but I wanted to make sure my issue was clear.