caching of data when using the new ODBC driver

The caching occurs on the HPCC side. A query will generate an internal Workunit ID (WUID) on HPCC's side.

However it seems that certain queries result in the same WUID and when this happens, the results returned from HPCC will always be the results of the first query that generated the WUID. We noticed this when working on ORDER BY support where changing the order from ASC to DESC, for instance, would still return the results for the ASC since it was issued first.

Running a stored procedure to execute a query always seems to generate a unique WUID so this problem does not happen. We've looked into a programmatic solution to remove these WUIDs before we run a query but haven't found any functionality to do this.

Suggested Work Around:
You can change either the “Username” or “result Limit” in the executes request.

Not recommended: deleting the WU programmatically, but there is a web service method to do that:
http://<yourHPCCESPIP>:<youreclwatchportusually8010>/WsWorkunits/WUDelete?ver_=1.55&wsdl