margelo / margelo/react-native-nitro-sqlite
missing error logging in batch transactions
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 565
- Forks
- 53
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 18
Description
When using .executeBatchAsync(statements) I always only get [SqlExecutionError] cannot rollback - no transaction is active when any of the statements fails. I would expect to get the sql error of the statement that produced the error. Is there any way to get the proper exception that caused the batchTransaction to fail?
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 by tracing the executeBatchAsync(statements) entry point and the handling of SqlExecutionError during batchTransaction rollback. Reproduce a failed batch with a statement that produces a SQL error, then verify that the original statement error is surfaced instead of only the rollback message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, react-native, sqlite
- Domain
- database, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100