Preserve SQLite configuration and serialization in macOS support

Open
#333 0 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
c, react-native, sqlite

Research direction

Compare PR #298 with current main, then review the thread-safety, performance-mode, and operation-serialization changes from #325, #328, and #326. Run the existing pod configuration checks and compile the merged native implementation. Done means retaining configuration validation, default thread safety, per-connection locking, and async buffer copying without unsafe defaults or lost connection lifetime protection.

Written by the indexing model from the issue text.

Description

PR #298 predates the thread-safety, performance-mode, and operation-serialization changes merged in #325, #328, and #326. Its merge conflicts can restore unsafe defaults or remove connection lifetime protection.

Merge current main into #298 while retaining its configuration validation, default thread safety, per-connection locking, and async buffer copying. Run the existing pod configuration checks and compile the merged native implementation.

Source: https://github.com/margelo/react-native-nitro-sqlite/pull/298

Dominant language
C
Stars
565
Forks
53
Avg merge
3d 13h
Merged PRs (30d)
28

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.