This driver behavior is not recommended. The cursor library implements a positioned update or delete SQL statement by creating a searched update or delete statement with a WHERE clause that enumerates the values stored in its cache for each bound column.
The cursor library passes calls to SQLFetch , on the other hand, through to the driver. Skip to main content. Yes Bulk load worked earlier when we were in 9. Recently we migrated to new DB2 version in azure, might be the reason. Will look at that and update. Error: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on and reload this page. Please enter a title. You cannot post a blank message.
Qlik Replicate Discussion board for collaboration on Qlik Replicate. Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for. Search instead for. Did you mean:. If the SQL statement that caused this error is hard-coded or built by the application, this is a programming error and the code needs to be fixed.
If the SQL statement is entered by the user, this is a user error and the application has done all that is possible by informing the user of the problem. However, there is no guarantee that all drivers return them. SQLSTATE HYC00 Optional feature not implemented is particularly significant because it is the only way in which an application can determine whether a driver supports a particular statement or connection attribute. Skip to main content.
0コメント