squibble: allow filtering of unmanaged tables#2
Merged
creachadair merged 2 commits intomainfrom Oct 30, 2025
Merged
Conversation
In some cases, a database may have tables that squibble should not treat as part of the update schema. We already have a couple examples of this, we filter out _schema_history (which squibble populates), and the sqlite_sequence table. Another example, as described in #1, are the tables created by the Litestream replication tool (https://litestream.io/). Add a field to the Schema type allowing the user to specify database and view names that should be excluded, and include those in the filter we apply when loading a schema for comparison.
creachadair
force-pushed
the
mjf/ignore-tables
branch
from
f756491 to
a5bdb7e
Compare
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
2 participants
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.
In some cases, a database may have tables that squibble should not treat as
part of the update schema. We already have a couple examples of this, we filter
out _schema_history (which squibble populates), and the sqlite_sequence table.
Another example, as described in #1, are the tables created by the Litestream
replication tool (https://litestream.io).
Add a field to the Schema type allowing the user to specify database and view
names that should be excluded, and include those in the filter we apply when
loading a schema for comparison.