3 ms·
True - but so much of the value of autocomplete comes from just being able to try things out: 'from customers, orders select ...' Would allow showing a whole
by jka 13y ago
True - but so much of the value of autocomplete comes from just being able to try things out:
'from customers, orders select ...'
Would allow showing a whole bunch of columns, and you could quickly determine whether those tables had the information you're after, or not.
It might seem strange/lazy that the developer can explore the environment (schema) this way without 'knowing' what's out there, but in practice that's exactly what we all do with software development, web search, etc - we try things out and see what comes back, rather than knowing in the first place. Data development has a way to go, but I think things will improve..
- jka 13y agoActually, one alternative approach would be: use a search index to autocomplete after even a basic 'SELECT' statement (no other context), but then fill the FROM clause based on the selection. i.e. - type: 'select city' prompts with: 'city (table airports)' 'city (table populations)' 'city (table companies)' And then, upon selection, you have a statement: 'select city from <selected-table>'. There's a lot more here though. Worth pondering for a while I think.