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

connect db2 when column is NULL, parsing data error execution an error occurred is {wrong column #1 length 4294967295 returned, 16 expected} #194

Open
samsung0-cpu opened this issue Mar 23, 2024 · 3 comments

Comments

@samsung0-cpu
Copy link

image
Why not return directly when encountering an parsing data error?

@alexbrainman
Copy link
Owner

Why not return directly when encountering an parsing data error?

I don't understand your question.

Alex

@samsung0-cpu
Copy link
Author

I found that when a certain column value is NULL, data parsing will throw a parsing failure message

@alexbrainman
Copy link
Owner

I found that when a certain column value is NULL, data parsing will throw a parsing failure message

I still did not understand your question above #194 (comment) .

Alex

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

No branches or pull requests

2 participants