Database migration schema
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
先阅读 Appwrite CLI 的迁移路径，以及 appwrite.config.json 的更改是如何应用的。复现一次 schema 更新和一次失败的多步骤 push，以了解当前行为。当现有数据在属性更改后仍然保留，并且失败的 CLI 迁移能够恢复上一个正常工作的 schema 时，即视为完成。
由索引模型根据 Issue 内容生成。
描述
🔖 Enhancement description
- Non-destructive / Seamless schema migrations: Changing an attribute (like its type or format) should not drop the column and wipe existing data.
- Atomic rollbacks: If an error occurs while applying schema changes via the CLI, the process should roll back to the last working state entirely, rather than leaving the database schema in a broken or partially updated state.
🎤 Pitch
In my opinion, the current “migration” via the Appwrite CLI and “appwrite.config.json” isn't really a migration at all.
The biggest problem: A single change to an existing attribute automatically leads to data loss, which is extremely critical in a production environment. And having to write a separate script for something like this isn’t worth the effort for such a basic task, in my opinion.
While this might be acceptable for side projects or early MVP stages, it becomes a massive deal-breaker when deciding whether to scale a SaaS product with Appwrite.
Furthermore, the lack of atomic rollbacks means if a CLI push fails halfway through, the schema doesn't revert to its last known good configuration, it simply breaks, leaving the database in an inconsistent state.
Feel free to correct me if I'm wrong.
👀 Have you spent some time to check if this issue has been raised before?
- I checked and didn't find similar issue
🏢 Have you read the Code of Conduct?
- I have read the Code of Conduct
- 主要语言
- Go
- 星标
- 103
- 派生
- 45
- 平均合并
- 3 小时 16 分钟
- 30 天内合并 PR
- 11
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 75/100
keyxmakerx/Chronicle#1721 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
Gentleman-Programming/gentle-ai#5720 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
ClickHouse/ch-go#1218 ·
维护者通常 13 天内回复
-
effort:s impact:low raised-by:reviewer risk:low
难度 1/5 1 小时以内 新手友好度 84/100
medici-finance/assay#4251 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 1/5 1-3 小时 新手友好度 88/100
Edwin-metcalf/MetCode#30 ·
维护者通常 1 天内回复