[expo-sqlite] Correct rowsAffected result value on iOS. #9317
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…ive tests to test-suite.
Why
As suggested in issue #3163 we return incorrect value in rowsAffected when executing cascade update/delete. It turned out, that whole rowsAffected logic is flaky.
How
Switchong from
sqlite3_total_changes
tosqlite3_changes
method and removing unnecessary logic.Test Plan
Added respective tests in
test-suite
.