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

Invalid Input Error #840

Closed
neelasha23 opened this issue Aug 28, 2023 · 3 comments · Fixed by #873
Closed

Invalid Input Error #840

neelasha23 opened this issue Aug 28, 2023 · 3 comments · Fixed by #873
Assignees

Comments

@neelasha23
Copy link

When running a select query without running the dataset download step I get error that file not found.

Screenshot 2023-08-28 at 4 56 25 PM

However, even after running the download step and rerunning I get the below error:

Screenshot 2023-08-28 at 4 56 47 PM

(I have repeated the steps by opening a clean notebook session and got the same set of errors)

@edublancas
Copy link

this isn't a bug per-se, but it'd be better if jupysql automatically performed the rollback.

we are already covering this for some PostgreSQL errors and we could handle this DuckDB edge case:

def _execute_with_error_handling(self, operation):

@bbeat2782
Copy link

Acceptance Criteria

  1. Ensure downloading and rerunning the select statement works as expected
  2. Add a test case for duckdb

@bbeat2782
Copy link

bbeat2782 commented Sep 7, 2023

demo.mov

I tried to replicate the error, but it works as expected on my local setting.

EDIT: I was using sqlalchemy==1.4.49. After upgrading sqlalchemy version to 2.0.20, I was able to replicate the error

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