-
Notifications
You must be signed in to change notification settings - Fork 14
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
easyaccess unresponsive after Oracle error #130
Comments
Thanks @coljac!. I haven't had much feedback from the Docker Image. You are right, after a error the image gets frozen. I think I know the reason and its related to running a subprocess from inside easyaccess. I'll try to debug it and get it fixed. Thanks again for reporting it |
I can report the same issue on a iMac running El Capitan (10.11.6). easyaccess hangs on any query after a cx_Oracle error in the previous query. Note that the error does not manifest itself if the error is not related to cx_Oracle: e.g. after trying to write out the results to a .txt file (which is not supported), I can re-run the query fine. |
thanks @wycombe7, I need to make sure this get fixed, regarding .txt, is not supported as extension but if you use .tab extension and those columns will be space-separated |
Thanks @mgckind for looking into this. If it helps, this is a problem that's only appeared (for me) in the latest version of easyaccess: version 1.4.2 ran smoothly without complaint. |
Hi @mgckind, |
Hi @mgckind, Has a solution been found for this problem? |
I'm running easyaccess using the docker container on the docker hub.
If I make a syntax error in a query, and get an error message from Oracle (printed in red by easyaccess), it returns me to the prompt but the subsequent command will not run, and the tool becomes unresponsive. I have to kill the docker container and start again.
To reproduce:
The text was updated successfully, but these errors were encountered: