Fix hard crash when describing "zero" datetime #64
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
…me is received from older MySQL configurations which still do this. Returns a description of the epoch instead.
…t dependency on the update NIOSSL version.
gwynne
force-pushed
the
fix-63-hard-crash-with-zero-time-data
branch
from
5571010 to
5b97bbe
Compare
… actually work yet.
Joannis
reviewed
Sep 8, 2021
Joannis
previously approved these changes
Sep 8, 2021
…ppears to be broken again and the workflow never completes.
0xTim
previously approved these changes
Sep 8, 2021
…d intermittent failures
|
These changes are now available in 1.3.3 |
|
Note - CI failures are a MySQL bug, not a driver issue |
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Fixes #63.
Also fixes a minor thread-safety issue and clears up deprecation warnings from NIOSSL.