Align rel table naming with upstream pg_client - #11
Open
adsharma wants to merge 1 commit into
Open
Conversation
Upstream ladybug-extension renamed the FK-backed rel table prefix: fkrel_ -> rel_, with csr_rel_ reserved for attach-time CSR materialization (not yet implemented, routed through the same scan-driven path as rel_). - scripts/test_with_pgembed.py: rename fkrel_knows -> rel_knows; the retired fkrel_ prefix is no longer auto-detected by pg_client - README.md: document the full naming convention including the reserved csr_rel_ prefix - test.sql: note the convention in the header comment Requires liblbug >= 0.20.0 for rel-table join pushdown; 0.19.1 returned a bare node-table scan for rel patterns.
adsharma
changed the title
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.
No description provided.