Skip to content

docs(features): hold keyed edits to matched rows on MySQL, SQL Server, Oracle, Snowflake, Dameng - #222

Merged
datlechin merged 1 commit into
mainfrom
docs/d-rowcounts
Nov 12, 2026
Merged

datlechin merged 1 commit into
mainfrom
docs/d-rowcounts

Conversation

@datlechin

Copy link
Copy Markdown
Member

Documents TableProApp/TablePro#4242.

  • features/change-tracking: a keyed edit that matched no row fails the save on MySQL, MariaDB, TiDB, OceanBase, SQL Server, Oracle, Snowflake and Dameng too; the cases that stay lenient (a gone row's delete, an edit after a delete, an edit through a view); Snowflake and Dameng hold the count after their lookup.
  • databases/mysql: new Rows affected section. An UPDATE counts the rows it matched, ROW_COUNT() agrees, ON DUPLICATE KEY UPDATE onto unchanged values reports 1.

@mintlify

mintlify Bot commented Nov 12, 2026 •

Copy link
Copy Markdown

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

Project Status Preview Updated
TablePro 🟢 Ready View Preview Nov 12, 2026, 6:40 PM

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

@datlechin
datlechin marked this pull request as ready for review November 12, 2026 20:50
@datlechin
datlechin merged commit ba5f03d into main Nov 12, 2026
2 checks passed
@datlechin
datlechin deleted the docs/d-rowcounts branch November 12, 2026 20:54

This branch was successfully deployed

1 active deployment
staging — cc2ca470 Deployed Nov 12, 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