Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

feat: bind named SQL parameters

未关闭
#402 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
cpp, react-native, sqlite

调研方向

Start by tracing the existing positional binding path for ordinary queries, prepared statements, and batch commands, including the shared native binding and error handling. Review the related issues for context, then identify the sync and async entry points and platform-specific paths. Done means named and positional bindings coexist across iOS and Android with the specified placeholder, missing-value, error, reuse, and batch behavior covered.

由索引模型根据 Issue 内容生成。

描述

area:api area:runtime enhancement

Query parameters are currently positional arrays. SQL that uses named placeholders must be mapped to positions by callers, which complicates reusable queries and adapters for other SQLite runtimes. Issue #62 asked for named bindings alongside the existing positional API.

Accept a record of names to SQLite values for ordinary queries, prepared statements, and batch commands while retaining positional arrays. Resolve each name with SQLite's parameter-index API and reuse the shared native binding and error handling. Specify the accepted key format for :name, @name, $name, and numbered placeholders; reject unknown keys and document how missing values behave. Do not log parameter values in errors.

Cover repeated named placeholders, mixed placeholder styles, NULL and undefined, BLOBs, sync and async calls, prepared-statement reuse, and batches on iOS and Android. Keep this separate from array-shaped result rows; the two API changes solve different problems.

Related: #62 and #382. The Node test-mock proposal in #395 already tracks the testing-adapter part of #62.

主要语言
C
星标
579
派生
53
平均合并
2 天 3 小时
30 天内合并 PR
70

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

margelo/react-native-nitro-sqlite 的其他 Issue

查看 margelo/react-native-nitro-sqlite 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。