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 better error messages #239

Merged
merged 5 commits into from
Jul 1, 2024

Conversation

apocelipes
Copy link
Contributor

For #238.

@apocelipes
Copy link
Contributor Author

This is ready for review.

@marcboeker
Copy link
Owner

Thanks @apocelipes, we'll have a look at it.

@marcboeker marcboeker requested a review from taniabogatsch June 28, 2024 20:29
Copy link
Collaborator

@taniabogatsch taniabogatsch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, @apocelipes, thanks for the PR! I agree that go-duckdb should support better error messages. I've left one main question: How should go-duckdb handle (or even just distinguish) between duckdb errors and driver errors?

errors.go Outdated Show resolved Hide resolved
errors.go Show resolved Hide resolved
errors_test.go Outdated Show resolved Hide resolved
@apocelipes apocelipes force-pushed the feat-better-error branch from 748cfc4 to c4a66b1 Compare July 1, 2024 12:17
@taniabogatsch taniabogatsch merged commit 2725c1c into marcboeker:main Jul 1, 2024
4 checks passed
@taniabogatsch
Copy link
Collaborator

Thanks for the contribution!

@apocelipes apocelipes deleted the feat-better-error branch July 1, 2024 12:52
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 this pull request may close these issues.

3 participants