Skip to content

docs: clarify diff connection routing #43

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.

Sign up for GitHub

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
kvlonge merged 1 commit into from
Sep 10, 2026
Merged

docs: clarify diff connection routing #43

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions concepts/diff.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,9 +12,11 @@ SQLBuild can compare schemas and row-level data between two build contexts. This

The mechanics below are identical for both; only what `FROM` and `TO` refer to changes.

In direct mode, each name resolves a configured target, including its named connection and
authoritative database/schema namespace. Unknown connection references fail during offline
configuration loading before SQLBuild attempts the comparison.
In direct mode, `FROM` and `TO` resolve the authoritative database/schema namespaces to compare.
SQLBuild uses the `TO` target's named connection for the complete comparison and accesses both
namespaces through fully qualified relations. It does not resolve or open the `FROM` target's
connection. The `TO` connection must therefore be able to read both namespaces; missing credentials
for that execution connection still fail before warehouse inspection.

```bash
sqb diff prod:dev --full --select customer_status_snapshot
Expand Down
Loading