Fix for #8139: Add lookup index name by constraint for correct resolve conflict on replica#8586
Merged
hvlad merged 1 commit intoFirebirdSQL:masterfrom Jun 6, 2025
Merged
Conversation
hvlad
reviewed
Jun 4, 2025
…rect resolve conflict on replica
hvlad
approved these changes
Jun 5, 2025
Member
|
Please, backport into v5 |
Contributor
Author
Separate PR? Or what is the best way to do it? |
hvlad
added a commit
that referenced
this pull request
Jun 11, 2025
Fix for #8139: Add lookup index name by constraint for correct resolve conflict on replica
hvlad
added a commit
that referenced
this pull request
Jun 11, 2025
Fix for #8139: Add lookup index name by constraint for correct resolve conflict on replica
Member
|
Backported into v4 and v5 |
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
2 participants
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.
No description provided.