You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FieldNames should load in ( and at the top of ) intellisense suggestions. So that three + bonus cases work below. As it is now, field names will load if you know what the field name is and type enough, but the fields should load after a space is typed after ['where', 'and', 'or', 'on','order by', 'group by','else', 'if']. There's probably something else but these are the big ones. Bonus points if you're as good as sqlPrompt (the model for this suggestion) if "having" clause brings up fields and the aggregate function at the top of the suggestion list.
Select * from A_Table where <--Intellisense brings up list of field names--> = "blah blah blah"
Select <--intellisense brings up field names--> from A_Table. -- Case 2 happens once the cursor is navigated back to the select after the table name is typed.
select * from A_Table AT join B_Table BT on <--intellisense brings up BT.column list--> = <-- AT.column list -->
Bonus. select count(first_names),first_names from Clients group by first_names having <--intellisense brings up "count(first_names)" as suggestion at top-->
I do understand that if you use: Select * from Z_Table zt
That typing "where zt."<-- intellisense kicks in with columns -->
Not having an alias column list would be like mashing potatoes with a fork. Your aliased solution is like having a hand masher tool (I have one, it's OK), but just bringing up the column list after keywords on keyboard space is the electric mixer of solutions.
The text was updated successfully, but these errors were encountered:
FieldNames should load in ( and at the top of ) intellisense suggestions. So that three + bonus cases work below. As it is now, field names will load if you know what the field name is and type enough, but the fields should load after a space is typed after ['where', 'and', 'or', 'on','order by', 'group by','else', 'if']. There's probably something else but these are the big ones. Bonus points if you're as good as sqlPrompt (the model for this suggestion) if "having" clause brings up fields and the aggregate function at the top of the suggestion list.
Select * from A_Table where <--Intellisense brings up list of field names--> = "blah blah blah"
Select <--intellisense brings up field names--> from A_Table. -- Case 2 happens once the cursor is navigated back to the select after the table name is typed.
select * from A_Table AT join B_Table BT on <--intellisense brings up BT.column list--> = <-- AT.column list -->
Bonus. select count(first_names),first_names from Clients group by first_names having <--intellisense brings up "count(first_names)" as suggestion at top-->
I do understand that if you use: Select * from Z_Table zt
That typing "where zt."<-- intellisense kicks in with columns -->
Not having an alias column list would be like mashing potatoes with a fork. Your aliased solution is like having a hand masher tool (I have one, it's OK), but just bringing up the column list after keywords on keyboard space is the electric mixer of solutions.
The text was updated successfully, but these errors were encountered: