ODBC: possibly returns wrong status after SQLCancel
Details
| Detail name | Value |
|---|---|
| Changelog Number | 4763 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | EXASOL 6.0.0, EXASolution 5.0.0 |
| Fix Versions | EXASOL 6.0.3 |
| Resolution Date | 2017-06-30 |
In asynchronous execution, EXA ODBC was possibly returning SQL_STILL_EXECUTING status after SQLCancel a few times for a already canceled or finished query before it returned the correct status (SQL_ERROR (HY008, Operation canceled) or SQL_SUCCESS).
This was because it was reading old status messages from the server. Starting with EXA ODBC 6.0.3 the user will always get the correct current status.
Changed behavior
In asynchronous execution, EXA ODBC was possibly returning SQL_STILL_EXECUTING status after SQLCancel a few times for a already canceled or finished query before it returned the correct status (SQL_ERROR (HY008, Operation canceled) or SQL_SUCCESS).
Starting with EXA ODBC 6.0.3 the user will always get the correct current status.
