perf: offer array-shaped query results
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 48/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- cpp, javascript, react-native, sqlite
- 领域
- database, mobile, performance
调研方向
Begin with PR #389's converter and the existing synchronous, asynchronous, and prepared-statement query entry points. Add coverage for both result modes, including duplicate aliases, NULL, text, numbers, BLOBs, and empty results, then compare narrow and wide full-row consumption on iOS and Android Release builds for conversion time and peak memory.
由索引模型根据 Issue 内容生成。
描述
Object-shaped results create a JavaScript object and set a property for every returned column. PR #389 removes the native row maps and an intermediate copy, but its converter still builds those JavaScript objects. For callers that consume wide results by column position, an array-shaped result may reduce conversion time and memory.
Add an opt-in result mode that returns each row as an array alongside column names in SQL order. Keep the existing object-shaped result as the default. The API should work for ordinary synchronous and asynchronous queries and prepared statements without creating a second SQL execution path. An ordered column list matters because duplicate aliases cannot be represented faithfully by the current metadata map.
Measure this against the object converter after #389 on the same Release builds. Include both narrow and wide queries, full row consumption, conversion time, and peak memory on iOS and Android. Preserve the old behavior for duplicate aliases in object mode and test NULL, text, numbers, BLOBs, and empty results in both modes.
Related: #30, #62, #389. The timings in #30 came from the old QuickSQLite implementation and are not an expected v10 speedup.
- 主要语言
- C
- 星标
- 579
- 派生
- 53
- 平均合并
- 2 天 3 小时
- 30 天内合并 PR
- 70
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
margelo/react-native-nitro-sqlite 的其他 Issue
-
area:api area:runtime enhancement
难度 5/5 一周以上 新手友好度 35/100
margelo/react-native-nitro-sqlite#402 ·
维护者通常 1 天内回复
-
area:api area:runtime enhancement
难度 5/5 一周以上 新手友好度 28/100
margelo/react-native-nitro-sqlite#401 ·
维护者通常 1 天内回复
-
area:api area:runtime enhancement
难度 5/5 一周以上 新手友好度 35/100
margelo/react-native-nitro-sqlite#400 ·
维护者通常 1 天内回复
-
area:api area:runtime enhancement
难度 5/5 一周以上 新手友好度 28/100
margelo/react-native-nitro-sqlite#399 ·
维护者通常 1 天内回复
-
area:api area:runtime enhancement
难度 5/5 一周以上 新手友好度 35/100
margelo/react-native-nitro-sqlite#398 ·
维护者通常 1 天内回复
查看 margelo/react-native-nitro-sqlite 的全部 Issue
相似的 Issue
-
rc_runtime_activate_richpresence leaves a half-initialised entry when the buffer allocation fails未关闭
难度 1/5 1 小时以内 新手友好度 88/100
RetroAchievements/rcheevos#558 ·
-
难度 2/5 1-3 小时 新手友好度 74/100
-
难度 2/5 1-3 小时 新手友好度 88/100
libsdl-org/SDL#16464 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
-
chore(gateway): emit INFO budget reserved/settled logs for proactivity v2 (chip task_2855f4ec)可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭backend
难度 2/5 1-3 小时 新手友好度 68/100
BasedHardware/omi#20940 ·
维护者通常 1 天内回复