Skip to content

Harden SQLite execution and lifecycle handling - #1

Merged
martian56 merged 4 commits into
mainfrom
audit/sqlite-hardening
Jul 15, 2026
Merged

martian56 merged 4 commits into
mainfrom
audit/sqlite-hardening

Conversation

@martian56

Copy link
Copy Markdown
Owner

What changed

  • add checked binding, stepping, reading, reset, finalize, timeout, and close APIs
  • preserve SQLite execution errors, embedded NUL text, and result column metadata
  • expand lifecycle, transaction, boundary, and large-value coverage
  • test Raven 2.26.1 on Linux and Windows
  • prepare version 0.2.0 with a changelog

Why

The original convenience APIs discarded several SQLite return codes, so constraint, binding, and close failures could be mistaken for normal completion. The checked APIs preserve compatibility while allowing callers to handle every database failure.

Validation

  • rvpm fmt --check
  • rvpm build
  • rvpm test (15 passed)
  • rvpm doc

@martian56 martian56 self-assigned this Jul 15, 2026
@martian56
martian56 merged commit 2089970 into main Jul 15, 2026
5 checks passed
@martian56
martian56 deleted the audit/sqlite-hardening branch July 15, 2026 09:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant