Skip to content

docs(features): say what each engine's restore keeps - #162

Merged
datlechin merged 1 commit into
mainfrom
docs/restore-confirmation
Nov 1, 2026
Merged

datlechin merged 1 commit into
mainfrom
docs/restore-confirmation

Conversation

@datlechin

Copy link
Copy Markdown
Member
  • Restore dump: the Confirm step links to a new per-engine table, Objects already in the database, in place of "Objects it names are overwritten".
  • The table says what PostgreSQL, MongoDB, MySQL, SQLite, DuckDB and SQL Server do with objects already there and at an error, matching the app's confirmation text.
  • SQLite: a dump that is not one transaction keeps what ran before the error, and a table created with a quoted name gets the dump's rows.

Documents TableProApp/TablePro#3984.

@datlechin
datlechin marked this pull request as ready for review November 1, 2026 09:50
@datlechin
datlechin merged commit 718c1c7 into main Nov 1, 2026
@mintlify

mintlify Bot commented Nov 1, 2026 •

Copy link
Copy Markdown

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

Project Status Preview Updated
TablePro 🟢 Ready View Preview Nov 1, 2026, 8:58 AM

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

This branch was successfully deployed

1 active deployment
staging — 1206634f Deployed Nov 1, 2026 by mintlify[bot]
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.

1 participant