extract-jdbc: cursor incremental query includes lb #44450
Closed
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced Aug 20, 2024
postamar
force-pushed
the
postamar_gt_08-20-extract-jdbc_add_greaterorequal
branch
from
7227541 to
23f0ac8
Compare
postamar
changed the title
postamar
force-pushed
the
postamar_gt_08-20-extract-jdbc_add_greaterorequal
branch
from
23f0ac8 to
efdfacf
Compare
postamar
force-pushed
the
postamar_gt_08-20-extract-jdbc_add_greaterorequal
branch
from
efdfacf to
6c36470
Compare
|
Closing because I'm merging the top of the stack #44482 into master using slash-approve-and-merge. |
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.
The cursor's lower bound value needs to be included in the WHERE clause because the cursor column values may be not unique; right now we're facing data loss for example if the cursor column is of type DATE DEFAULT NOW() and rows get inserted after a daily sync but on the same day.