|
From: Colin B. <col...@te...> - 2002-10-17 22:56:54
|
Hi Christian, Sorry for the late response to your emails, I'm incredibly busy at the moment and email is one of those things that gets put to the bottom of the list. > I have now reached a point where completion for all DML statements works > fairly well (I hope). I have also created a SQuirrel plugin, which is > based on the default entry panel (see doc/readme.html). This should be a > better demonstration than the little program before. I'll have a look at it. > The "Table/Column Chooser" is a hack - maybe someone with more swing > enthusiasm can give a hand here. It seems rather inefficient to load all > tables into the list - maybe there should be a facility to narrow the > selection before it is displayed. It would be nice just to see tables that start with the characters they typed prior to calling for completion. Also is there any way to get schema/catalog info (possibly with a different cmd key) completion? An example SQL select * from othercatalog.table1, myTable where ... Here we are joining from a table in the current catalog (myTable) to one in a different catalog (table). Would it be possible to key in 'oth' CtrlSpace and have the catalog names pop up? > > The completion itself needs to be tested. It can also be made yet more > intelligent. DDL statements are not supported (but what would you want > to complete there?). Possibly foreign key relationships? > My development progress will now be much slower for a while, because I > have been called upon by a customer. This will keep me rather busy until > the end of the year. If anyone has something to contribute - go ahead > and let me know. Just as its starting to look good too. I know Russell was interested, maybe he could give you a hand. Russell? > BTW, I did not find any easy way to debug plugins from within my IDE. I > ended up creating a "dummy" jar file with just the XxPlugin class > inside, and keeping that in the appropriate directory for Squirrel to > load. I could then debug the rest of the code as usual. Do you have any > better suggestions? Your method sounds better than mine. I actually generate a jar file for the plugin containing all the class files and place it within my project directory. I then tell the debugger where the source for these classes reside. This means that whenever I make a change to a plugin I have to rebuild the jar, if I forget I'm debugging the wrong code. Col -- Colin Bell http://squirrel-sql.sf.net |
