fix binding strings with nulls; update param type tests#147
Merged
jraymakers merged 1 commit intomainfrom Feb 8, 2025
Merged
Conversation
Collaborator
Author
|
The DuckDB bug mentioned in the description is filed here: duckdb/duckdb#16137 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Use the
_lengthvariants of C API functions that take C strings where possible, to handle embedded null characters properly. This was visible through the API in at least one case (binding VARCHARs with embedded nulls). Added a test for this case.Also update the
param_typetests now that it works in more cases. But I found a new bug in 1.2.0, whereparam_typereturns INVALID for VARCHARs (only). I've confirmed this is a bug in DuckDB and am filing an issue there.