Skip to content

Document a known limitation regarding affected row count #202

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

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

Document a known limitation regarding affected row count #202

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
19 changes: 19 additions & 0 deletions docs/known-limitations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
# Known limitations
This file documents the known limitations of the SQLite driver that are difficult
to address and are not currently planned to be resolved.

### Number of affected rows when values are not changed
In some cases, the number of affected rows reported by the SQLite driver may
differ from the number returned by MySQL. This is because SQLite always reports
the number of rows matched by a statement, regardless of whether they were
actually changed or set to the same values as they already held.

Example:

```sql
CREATE TABLE t (id INT);
INSERT INTO t (id) VALUES (1);
UPDATE t SET id = 1;
```

The `UPDATE` statement above reports `0` affected rows in MySQL, but `1` in SQLite.