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

Overriding sqlalchemy error handling #229

Closed
idomic opened this issue Mar 12, 2023 · 2 comments · Fixed by #400
Closed

Overriding sqlalchemy error handling #229

idomic opened this issue Mar 12, 2023 · 2 comments · Fixed by #400
Assignees

Comments

@idomic
Copy link

idomic commented Mar 12, 2023

When running Jupysql with a faulty query for instance (I believe that's the main place it happens), the user is left with a cryptic error message, I believe there are 2 improvements we can take.

  1. Show a detailed error message - perhaps even show where the query faulted (analyze it on the fly).
  2. Presenting the community link so users know they can get help and follow up on the next step.

Screen Shot 2023-03-12 at 10 38 54 AM

@edublancas
Copy link

Yeah, I agree this is something important we can fix. The challenge is that each db driver raises different types of errors. But at least we can detect the most common ones for the most popular dbs

@idomic
Copy link
Author

idomic commented Mar 13, 2023

Example on postgress via psycopg-2
Screen Shot 2023-03-13 at 2 02 23 PM

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

Successfully merging a pull request may close this issue.

3 participants