Skip to content

Conversation

NattyNarwhal
Copy link
Member

I have no idea why it's using strlen in the first place, but if SQL/CLI returns junk in the buffer, then the length might be correct. This matches what we did with column names on IBM i.

The SQL_BINARY case is more puzzling, but we can take a look at it later if this works for strings. Why is it ifdef'd to use strlen/out_length depending on platform?

I have no idea why it's using strlen in the first place, but if SQL/CLI
returns junk in the buffer, then the length might be correct. This
matches what we did with column names on IBM i.

The SQL_BINARY case is more puzzling, but we can take a look at it later
if this works for strings. Why is it ifdef'd to use strlen/out_length
depending on platform?
@NattyNarwhal NattyNarwhal marked this pull request as ready for review October 7, 2025 16:45
@NattyNarwhal
Copy link
Member Author

This does seem to resolve the issue the user was having on IBM i after some testing. I suspect binaries should be covered under this too (considering those are supposed to be able to tolerate nulls)...

@NattyNarwhal NattyNarwhal merged commit 562fd86 into master Oct 7, 2025
12 checks passed
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.

1 participant