Skip to content

Document handling MSSQL schema changes - Service v1.25 - #568

Open
benitav wants to merge 4 commits into
mainfrom
mssql-schema-change-handling
Open

Document handling MSSQL schema changes - Service v1.25#568
benitav wants to merge 4 commits into
mainfrom
mssql-schema-change-handling

Conversation

@benitav

@benitav benitav commented Aug 17, 2026

Copy link
Copy Markdown
Collaborator

Resolves #555

I also had Claude check whether all latest error codes are documented using the corresponding script in the powersync-service repo.

AI usage: Drafted by Claude after giving it the original PR and docs drift issue as context. I reviewed the details against this changeset and they appear in line, but this PR still needs a more thorough review for technical accuracy.

@mintlify

mintlify Bot commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
powersync 🟢 Ready View Preview Aug 17, 2026, 12:49 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Comment thread configuration/source-db/setup.mdx
Comment thread maintenance-ops/implementing-schema-changes.mdx

@stevensJourney stevensJourney left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Drift] MSSQL replication pins to a capture instance, drops wildcard tables and auto schema-change handling (powersync-service #727)

2 participants