store: ensure consistent id type in FindRangeQuery SQL output #6080
Conversation
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
incrypto32
reviewed
Jul 17, 2025
shiyasmohd
force-pushed
the
shiyasmohd/fix-subgraph-composition-diff-entity-id
branch
7 times, most recently
from
56e2f5a to
f1151a6
Compare
shiyasmohd
force-pushed
the
shiyasmohd/fix-subgraph-composition-diff-entity-id
branch
from
f1151a6 to
5a52078
Compare
|
@incrypto32 Changes:
|
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.
When using subgraph composition and indexing entity of different type
id, the subgraph wouldn't sync due to the below errorThis was because the
FindRangeQuerySQL generator wasn't casting entity IDs to a consistent type, causingUNION ALLoperations to fail when merging results from subgraphs with different ID types