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

Open samsung0-cpu opened this issue 1 year ago • 3 comments

Why not return directly when encountering an parsing data error？

Mar 23 '24 22:03 samsung0-cpu

Why not return directly when encountering an parsing data error？

I don't understand your question.

Alex

Mar 23 '24 23:03 alexbrainman

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

Mar 25 '24 01:03 samsung0-cpu

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 https://github.com/alexbrainman/odbc/issues/194#issue-2204074351 .

Alex

Mar 27 '24 06:03 alexbrainman