missing error logging in batch transactions

Open
#183 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp, react-native, sqlite
Domain
database, mobile-dev

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.

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?

Dominant language
C
Stars
565
Forks
53
Avg merge
2d 23h
Merged PRs (30d)
27

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from margelo/react-native-nitro-sqlite

All issues in margelo/react-native-nitro-sqlite

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.