-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cleanup whitespace and comments in SQL query text #1246
Merged
timvaillancourt
merged 8 commits into
github:master
from
timvaillancourt:fix-sql-whitespace
Dec 8, 2023
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
1e1e42d
Cleanup whitespace in SQL query text
timvaillancourt dae0482
cleanup
timvaillancourt 4042892
Add indent
timvaillancourt 6f1de5d
Update unit tests
timvaillancourt 704c412
Update unit tests, pt 2
timvaillancourt 7766a35
Fix tweaks
timvaillancourt eac4234
Merge branch 'master' into fix-sql-whitespace
timvaillancourt 17e8fba
Fix merge conflict resolution
timvaillancourt File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@timvaillancourt Does the time zone set here need to be configured as
this.migrationContext.ApplierTimeZone
? I noticed that other sessions are usingthis.migrationContext.ApplierTimeZone
for setting the time zone, but here it is set to +00:00. Should this be adjusted?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@shaohk good question, that sounds more correct than
+00:00
🤔Based on the soak testing this logic has seen I don't think this causes an integrity problem, however. I think that may be because binlog row events contain the values from that primary/master (including dates/times), so it probably doesn't matter what timezone the applier session uses here. I believe
gh-ost
is using the decoded binlog row event values onlyFewer "what if?" questions is a good thing though, so I would still welcome this change if it passes integration testing at GitHub