Repository navigation
fix(pg18): unpack array params for IN clauses; adopt core 0.3.1 list helper #26
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
10 commits
Select commit
Hold shift + click to select a range
bdcfe51
fix(search): replace ANY($N) with IN ($1,$2,...) for PG18 compat
smart-knowledge-systems 579eac1
fix(search): replace ANY($N) with IN ($1,$2,...) in query.ts
smart-knowledge-systems 5335338
fix(xref): replace ANY(\${arr}) with IN \${sql(arr)} for PG18 compat
smart-knowledge-systems c6f5b01
fix(dedup): replace ANY array params with IN placeholders for PG18
smart-knowledge-systems 2d5b00a
fix(mcp): replace ANY array params with IN placeholders for PG18
smart-knowledge-systems d8b7132
chore(deps): bump @easier-idx/core to 0.3.1, drop xref cast workaround
smart-knowledge-systems 546ee75
refactor(repo): use createPgStoreOps/createSqliteStoreOps from core 0…
smart-knowledge-systems 960d16d
Merge branch 'main' into fix/bun-pg18-array-encoding
smart-knowledge-systems ef1fc4f
fix(dedup): scale countBlobsExcept/deleteBlobsExcept past 65535-hash …
smart-knowledge-systems 6c3b0d5
refactor(search): reuse single placeholder set in withCrossRepoEdges
smart-knowledge-systems 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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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.
$Nplaceholder reuse is valid but inconsistent with sibling codeThe
getCrossRepoEdgesquery uses the sameplaceholdersstring ($1,$2,…$N) for bothsource_repo_id IN (…)andtarget_repo_id IN (…), passing a single copy ofscopedRepoIdsinparams. PostgreSQL's wire protocol supports$Nreuse within a query, so this is functionally correct. However,withCrossRepoEdgesinsrc/search/query.tshandles the same pattern with separateplaceholders/placeholders2index ranges and two copies of the array — a style divergence that may confuse future readers. Consider aligning to one convention.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!