v2.5.11
This release fixes a number of inconsistencies around prepared statements
when closeCursor()
is called, or when a prepared statement is re-used
multiple times.
Total issues resolved: 5
- 2487: Store results of subsequents statement executions same as of the first one
- 2489: Rebind row values to the statement after freeing result
- 2536: Bind result variables after each execution in order to prevent string truncation
- 2546: Prepared statements become unusable after calling closeCursor() on IBM DB2, Oracle and MS SQL Server.
- 2557: Inconsistent semantics of close cursor