Fix reading NULL Big Int data types. #58
Open
Conversation
This file contains 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
…e connection with Cassandra.
… bug with socket_connect. Now you can correctly control the socket timeout and the attempts to connect to server.
…ax attempts are reached.
…tempts. Code clarified to a better reading. Added a more precise error control over socket error codes. This will avoid php process being hanged when no server is available.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There is a bug when you have a NULL column from Big Int data type. The code throws the message "Reading while at end of stream" and gives a PHP Notice.
To fix this, the protected function "read()" must check if the length of the data being read returns false. If the column is NULL, then $length will be 0 and the error will be thrown.
This commit fixes this issue.