margelo / margelo/react-native-nitro-sqlite
Reset persisted benchmark schemas after app restarts
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 565
- Forks
- 53
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 18
Description
The benchmark database survives app restarts while its module-scoped connection does not. Reopening it currently attempts to create an existing Test table and prevents the benchmark from running.
Extract the reset fix and its native regression test from PR #298. Recreate the benchmark schema transactionally and verify replacement of an incompatible persisted table.
Source: https://github.com/margelo/react-native-nitro-sqlite/pull/298
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with PR #298 and its native regression test to identify the reset fix and the benchmark schema setup. Recreate the benchmark schema transactionally and verify that reopening the app replaces an incompatible persisted Test table; done when the benchmark runs after restart and the regression test passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, react-native, sqlite
- Domain
- database, mobile-dev, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100