drop nulls in connection history db #6339
Merged
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
jmcphers
approved these changes
Feb 27, 2020
kevinushey
force-pushed
the
bugfix/connections-history-drop-null
branch
from
cc6e147
to
1a8f48a
Compare
kevinushey
force-pushed
the
bugfix/connections-history-drop-null
branch
from
1a8f48a
to
5412569
Compare
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.
Band-aid for #6336.
Given that we don't have a reproducible example and (AFAIK) I'm the only one who's hit the problem, it may be better to take this for v1.4.