Repository navigation
setting time_zone on DML apply - #175
Merged
Merged
Conversation
Contributor
Author
|
Obsoletes #165 |
Contributor
Author
|
@dveeden are you able to test this branch on your side? |
Contributor
Author
|
Insofar this passes tests on my side; however the problem never manifested on my side in the first place. I'll only merge this on Monday, pending approval by @dveeden |
Contributor
Author
|
Testing passes. Am also working on local tests to verify this particular error, in separate PR. |
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
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.
Storyline: #161
This addresses the
time_zonesetting by applying a sessiontime_zonefor each and every DML applied, within same transactioncc @dveeden
gofmt(please avoidgoimports)./build.sh./test.sh