Name the path and the real failure when SQLite cannot use a database file
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start in dbkit/sqlite where the database path is opened and checked, and in the Classify function the issue names as the place to map SQLite failures to messages. Reproduce the four cases in the table (folder, non-database file, read-only file, file in a read-only folder) and see which prefix each one currently gets. Done means each case returns an error that names the path and states the cause, and the "read the database path" prefix appears only for read failures. The payload names no test file.
由索引模型根据 Issue 内容生成。
描述
What
When a SQLite address names something SQLite cannot use, dbkit/sqlite v0.1.0 lets the handle open and the first statement fails with an unclear error. Measured with Gophenberg, which opens through dbkit/sqlite:
| The path names | First statement fails with |
|---|---|
| a folder | dbkit: read the database path: unable to open database file (14) |
| a file that is not a database | dbkit: read the database path: file is not a database (26) |
| a read-only file | dbkit: read the database path: attempt to write a readonly database (8) |
| a file in a read-only folder | dbkit: read the database path: ... (1544) |
Two things are off:
- The prefix says "read the database path" even when SQLite failed a write.
- No message names the path, so the operator cannot tell which file is wrong.
Why
An operator who points a site at the wrong file should learn which file and what is wrong with it, for example "is a folder, not a database file" or "is read only". Classify and the open-time file check in dbkit/sqlite are the natural place, so every product on dbkit gets the same answers.
- 主要语言
- Go
- 星标
- 69
- 派生
- 3
- 平均合并
- 9 小时 11 分钟
- 30 天内合并 PR
- 38
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
gopherium/framework 的其他 Issue
-
bug help wanted
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
enhancement help wanted
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
enhancement help wanted
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
enhancement help wanted
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
enhancement help wanted
难度 3/5 1-2 天 新手友好度 65/100
维护者通常 1 天内回复
查看 gopherium/framework 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
ClickHouse/ch-go#1218 ·
维护者通常 13 天内回复
-
automation models
难度 1/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 77/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
-
难度 2/5 1-3 小时 新手友好度 72/100
podman-container-tools/podman#30031 ·
维护者通常 1 天内回复