-
-
Notifications
You must be signed in to change notification settings - Fork 288
fix(datagrid): restore FK jump arrows lost after sort, filter, or paginate #1663
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
ef3ff65
fix(datagrid): restore FK jump arrows lost after sort, filter, or pag…
datlechin a907afc
fix(datagrid): trace the FK metadata pipeline with structured logging
datlechin 784a405
fix(plugin-postgresql): read foreign keys from pg_catalog so non-owne…
datlechin 6276f02
fix(datagrid): rebuild FK column kinds before reloading cells after m…
datlechin 94a05ef
refactor(coordinator): clean up the FK metadata pipeline
datlechin File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On PostgreSQL servers older than 9.4, this new
WITH ORDINALITY/multi-arrayunnestsyntax is a parse error, so FK metadata fetches fail and the grid never marks foreign keys as fetched. The plugin still has explicit compatibility gates for older PostgreSQL versions (for examplehasMaterializedViewsCatalogat 9.3 and the guardedarray_positionuse), so this replaces a broadly compatibleinformation_schemaquery with one that breaks those supported connections; add a version-gated fallback or avoid the 9.4-only syntax here and in the matchingfetchAllForeignKeysquery.Useful? React with 👍 / 👎.