Skip to content
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

Support Oracle driver 4.0.0 #3396

Closed
kibertoad opened this issue Aug 14, 2019 · 8 comments
Closed

Support Oracle driver 4.0.0 #3396

kibertoad opened this issue Aug 14, 2019 · 8 comments

Comments

@kibertoad
Copy link
Collaborator

Currently tests are failing when latest Oracle driver is used.

@elhigu
Copy link
Member

elhigu commented Aug 16, 2019

I should take a look what causes it. Previously there has been bugs in new versions of oracle drivers.

@PeterMerkert
Copy link

PeterMerkert commented Aug 21, 2019

Maybe we should write down the errors which are happening? That would help to find this issue.

I have now the following one popping up: Error: ORA-12519: TNS:no appropriate service handler found. That seems to create a timeout my Ava test can not handle properly.

Edit: This error was occurring due to an internal Oracle ATP 18c bug.
I am actually using the driver version 4.0.1 of oracledb with latest knex 0.19.4 and I cannot complain about problems. But likely that I do not use all the functionality.

@kibertoad
Copy link
Collaborator Author

@PeterMerkert Are you using blob functionality? I think that's the part that is failing.

@PeterMerkert
Copy link

@kibertoad Nope, I am not using any blob functionality. I use select, several joins join, update, delete and raw statements.

@elhigu
Copy link
Member

elhigu commented Oct 23, 2019

Was this fixed by #3480 ?

@kibertoad
Copy link
Collaborator Author

Should have been, yes.
@PeterMerkert Could you please try using 0.20.0 and report back?

@PeterMerkert
Copy link

I got the upgrade and for me all my features are still working. The new version is in my code.

But remember, I have reported before that I did maybe not use the functionality which was broken in the first place.

Thanks a lot for the new version though anyways!

@kibertoad
Copy link
Collaborator Author

@PeterMerkert Awesome, I was wondering if we broke something while fixing something :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants