Fix duplicate column name in bi-temporal union queries with self-join associations - #4975
Open
wendy-nweje-gs wants to merge 1 commit into
Open
Conversation
gs-opensource-bot
force-pushed
the
review-fix-duplicate-milestone-column-regression
branch
from
July 23, 2026 14:17
c5831af to
7a1979b
Compare
Test Results 1 055 files - 6 1 055 suites - 6 2h 55m 57s ⏱️ - 1h 23m 40s Results for commit 7a1979b. ± Comparison against base commit 8740a07. ♻️ This comment has been updated with latest results. |
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
1 participant
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.
What type of PR is this?
What does this PR do / why is it needed ?
Which issue(s) this PR fixes:
Fixes #
Other notes for reviewers:
Does this PR introduce a user-facing change?