Memory Leaked Fixed in the c-treeSQL ODBC PRESERVE CURSOR Feature

A memory leak was found in the c-treeSQL ODBC driver when using the PRESERVE CURSOR feature.

When the executing a SQLFetch() on a query with an empty result set, the cursor becomes closed (or not even opened), however, at the application level the odbc cursor is open. If the cursor is then closed with SQLFreeStmt(SQL_CLOSE), as on the server side it is already closed, the logic fails with a SQL_ERR_NOTOPENED error and a free memory operation fails to take place.

To ensure the memory is freed, the SQL_ERR_NOTOPENED error is now ignored.