Support tables outside the public schema - #142
Merged
Merged
Conversation
Contributor
📊 Benchmark ResultsCurrent run is the minimum over 3 passes, compared against the base branch (
Summary: ➡️ 7 neutral · 🔴 3 slower · ⚪ 3 ignored (sub-μs) Thresholds: <1μs ignore · 1–20μs 15% · 20–50μs 10% · ≥50μs 5%. Measured on a shared CI runner — treat small deltas as noise. Informational only; this check never fails the build. |
Owner
Author
|
/bench |
1 similar comment
Owner
Author
|
/bench |
Owner
Author
|
/bench |
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
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.
Closes #50.
Streams could only target the
publicschema: startup validation hardcoded it andmatchStreamsdropped any change from another schema, even when the table name collided.resourceis a fully-qualified name (schema.table) end to end. The Postgres converter emits it andmatchStreamscompares it as an opaque string, so routing stays source-agnostic (no schema concept in the domain).public.<name>; writeschema.tableto target another schema.meta.schemais removed andmeta.resourcenow carries the qualified name (public.users, wasusers). v0, noted in the changelog.