Thanks for explaining that to folks. That's why we have the Query button.
To be a bit more precise, changing the selected query triggers a query. In your example, the selected query is not changed by clearing the cache so the application does not know to re-query.
In principle, we could have re-queried after Clear (and certain other button clicks) ... but that would have interferred with some of the DevForce exploratory scenarios.
For example, I like to show that the app keeps working after you disconnect ... but you get no query results if you then re-query when the cache is empty. To illustrate this, I could prescribe the sequence {Disconnect, Clear}. But I found that I myself often went {Clear, Disconnect}. If we were to auto-re-query, the first path would return the expected "no results"; the second path would always return the orginal results ... which I think would confuse people.
Can you see why?
Hint: {Clear, Disconnect, Clear} would do the job; there would be no displayed results.
Rather than have to explain all of this upfront, we decided that auto-query would occur ONLY on application launch.