Compare MySQL server and client time method. #174
Merged
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.
Summaries
@hito4t
This is the same implementation embulk/embulk-input-jdbc#106
This PR enable the embulk-output-mysql compare between a server and client timezone.
After comparison, output the following logs.
Test environment.
TZ=UTC mysql.server start
load data
time
is the important field.Test summaries
options: { useLegacyDatetimeCode: false, serverTimezone: UTC }
options: {}
options: { useLegacyDatetimeCode: false }
log
Case1
Case2
inserted wrong time.
Case3
Got runtime exception.