-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection.set_current_schema() fails #5
Comments
This issue still applies as of version 2.0.5.12-0. |
The extended message text for SQLCODE -5024 is this:
For some reason, the database is not handling the string properly when passed as UTF-8. It does seem to work if I hack it to pass as SQL_C_WCHAR (UTF-16) as noted from the message help, but that would be difficult to handle for just I did find that there is a connection attribute that does exactly what is wanted and works: Let me know if the |
Using ibm-db 2.0.5.9 from IBM i repo.
Connection.set_current_schema() fails with exception:
Internally, it executes the prepared statement "set current schema = ?" with proper parameter, and that's where the exception is thrown. A workaround is to concatenate directly (improper).
Here's a few tests, just change "schema" to an existing one on the system. The first three fail with the above exception.
The text was updated successfully, but these errors were encountered: