Wabit uses the DefaultStatementExecutor instead of the QueryCache to execute text statements.

[GoogleCodeExporter]

The QueryCache in the QueryPanel should be used as the statement executor
in the SQLQueryUIComponents embedded in the QueryPanel. However, from the
post at http://www.sqlpower.ca/forum/posts/list/2175.page the stack trace
shows the DefaultStatementExecutor being run when the SQL text side of the
editor is used. This means that when the text side is updated layouts using
the query will not be updated as the QueryCache that has the result set
cached will not update it.

Original issue reported on code.google.com by ThomasOB...@gmail.com on 5 Mar 2009 at 9:12

[GoogleCodeExporter]

This is temporarily fixed by defining the QueryCache in Wabit to be the
StatementExecutor in the SQLQueryUIComponents and uses it to override the text
execution method in SQLQueryUIComponents. We need to come back to this and find 
out
why the SQLQueryUIComponents does not get the QueryCache properly passed in when
using the text side of Wabit and remove the StatementExecutor from the
SQLQueryUIComponents constructor.

Original comment by ThomasOB...@gmail.com on 9 Jul 2009 at 8:24