Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.1.11
-
CentOS7 on Google Compute Engine, unixODBC 2.3.1, all ODBC drivers tested
Description
If using CONNECT engine ODBC with OPTION_LIST='Memory=3' and you run a query that produces a zero record result set, you get an error message as follows:
Got error 174 'Result set memory allocation failed' from CONNECT |
The expected result is just a zero record result with no error.