Conversation
lazerg
force-pushed
the
fix/gh-23758-empty-blob
branch
from
September 18, 2026 21:13
14e9334 to
d22da5e
Compare
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.
php_firebird_fetch_blob()only assigns the fetched string when the BLOB has a non-zero length, so a stored empty BLOB left the result zval at the NULL that PDO initialises it to. Callers could not tell an empty BLOB apart from SQL NULL, even though Firebird stores them distinctly.An empty BLOB now yields an empty string. SQL NULL still returns null, since that case is handled earlier in
pdo_firebird_stmt_get_col().Fixes #23758