This repository was archived by the owner on Jan 28, 2021. It is now read-only.
sql: correctly handle nulls in SQL type conversion #753
Conversation
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
juanjux
approved these changes
Jun 18, 2019
Contributor
|
@erizocosmico could you have a look to Travis? I'm facing the same error with: |
Signed-off-by: Miguel Molina <[email protected]>
erizocosmico
force-pushed
the
fix/handle-nil-sql
branch
from
24546b6 to
084fa59
Compare
Contributor
Author
|
Should be fixed now. One test was not correctly adapted. |
ajnavarro
approved these changes
Jun 19, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Will fix src-d/gitbase#878
Apparently, we've been handling nulls the wrong way all along when converting data to send to MySQL.