-
Notifications
You must be signed in to change notification settings - Fork 147
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
DB2 jdbc driver throws errors at end of query #379
Comments
Can you do |
It looks similar to #291. If the cause is the same, we should fix them both. |
|
I have found if I connect using the following format it works fine:
I got that custom parameter from the linked page in the original report. |
Thanks, @slords. Glad you found a workaround. Maybe others can use it. The stack is really helpful. I'll work on a fix. I don't have access to DB2 so I may ask you to help test it. |
@slords, Please try the latest master (3fadb13) and let me know whether it fixes the problem. I used PR #294 by @madeye-matt. |
Nope. Still getting the same error:
|
Would it be possible to have the parameter I'm setting manually in the connect string added to the project as one of the dbinfo parameters? DB2 doesn't support the type 2 jdbc driver anymore and their type 4 will always behave this way. The program is already so smart to know how to quote columns/tables/etc depending on the database type. This would just be one additional "smart" configuration. |
I don't think that's a good idea. The problem occurs in other drivers too (e.g. #291 is SQLite) so let's solve it once and for all. Can you please build and test against https://github.com/julianhyde/sqlline/tree/379-closed? I have made another attempt at a fix. |
I don't see that this branch is any different then the last test I did (3fadb13). I've already tested this and it failed with the same error and verbose output as shown. Was there more you wanted tested? |
Oops, sorry, I forgot to push 8a01ffc. Can you please try now. |
That appears to have fixed it. |
@julianhyde I discovered the exact same issue while trying to upgrade sql-phoenix to use sqlline 1.9. It's also caused by SQL-Phoenix closing the resultset as soon as it reaches the end, so this patch should fix it. Any idea for a release date?
|
I don't know when the next release will be. |
https://www.ibm.com/support/pages/invalid-operation-result-set-closed-error-data-server-driver-jdbc
When issuing a query against db2 I'm getting the following error:
Driver being used is:
The text was updated successfully, but these errors were encountered: