add a case in Next scan to fix issue #190 and issue #316 #468
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I get a same error as in #190 and #316 when I select a nullable datetime typed column
created_at
in one table:then I use
COALESCE
andCAST
to give it a default value and cast it as text:and I get the same error.
So I add a case to the
Next()
scan to give datetime typed column a chance to be parsed. After that issue #190/#316 and my problem are all fixed.I'm not sure if this's the right approach to the problem, here's twice benchmark results run on my computer:
Thanks~