(mysql.info) nocursor
Info Catalog
(mysql.info) transaction
(mysql.info) functionality
(mysql.info) myodbc-compatibility
23.1.14.4 What Causes `Cursor not found' Errors?
................................................
This occurs because the application is using old MyODBC 2.50 version,
and it did not set the cursor name explicitly through SQLSetCursorName.
The fix is to upgrade to MyODBC 3.51 version.
Info Catalog
(mysql.info) transaction
(mysql.info) functionality
(mysql.info) myodbc-compatibility
automatically generated byinfo2html