Passing in a non-escaped table to the lsn lookup function #85
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
s7clarke10
changed the title
|
Note: Checkng this in Meltano to ensure the ingestion works as expected. I have verified that this has resolved the issue 😊 |
s7clarke10
changed the title
mjsqu
approved these changes
Oct 9, 2024
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 SQL Server function sys.fn_cdc_get_min_lsn should receive an unescaped table name (because this is a function an the input should be a parameter in single quotes - not an escaped table in double-quotes).
The resolution to this issue is to provide an unescaped table to the
get_lsn_available_rangefunction.This will resolve #83 .