Fix: Skip MotherDuck internal cache tables in replacement scan #7
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
When using DuckDB WASM with both MotherDuck and duckarrow attached, MotherDuck's internal cache tables (mdClientCache_*) were being intercepted by the replacement scan and forwarded to GizmoSQL. - Add ShouldSkipTable() to validation package for testability - Skip tables matching mdclientcache_* prefix (case-insensitive) - Add comprehensive unit tests for skip logic
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.
Summary
mdClientCache_*) in replacement scanvalidation.ShouldSkipTable()for testabilityTest plan
make test-unitpasses with newTestShouldSkipTabletestsselect * from my_db.ApiEvent order by createdAt desc LIMIT 100;