Menu
▾
▴
#72 DB-based Autocompletion not very helpful
SQL Explorer has the ability to do column-based and table-based word completion (or so the documentation, bug reports here and the interface suggest), but here's the catch: it's not particularly useful in its current state:
1) When I'm using a database, I can't do "select * from tb_<complete key>" -- doesn't work. I can, however, do "select * from <dbname>." and auto-complete starts working -- so I have to go through the full hierarchy of <dbname>.<schema>.<tablename> to get to a table -- not all that useful for boosting the speed of development ):
2) I can't get column completion to work. Ever. Not even if I start with the database.schema.table that I mention above. I get nada. When SQL Explorer connects to my server, I can see it spending time figuring out completion information, but I don't actually get any usefulness from this.
Please note that I have enabled table/column completion in the preferences dialog. I'm using 3.5.1 (updated over the web this morning to the latest available), connecting to an MSSQL server using v 3.0 of the MSSQL JDBC driver. This is also all on win7, using the SQLExplorer bundle containing the x86 JRE.
I have the same problem with Oracle 9.2 and OJDBC12. This is really PITA and makes autocompletion useless.