Migrations that add new field to NpgsqlTsVector SearchVector
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start by reproducing the two migration scenarios described: adding an NpgsqlTsVector property alongside new fields, and changing an existing vector to include a new field. Inspect the generated migrations and the errors when applying them; the payload names no specific files or tests. Done means establishing whether a supported migration path exists for both cases and documenting or fixing it.
由索引模型根据 Issue 内容生成。
描述
Greetings! I was experimenting with NpgsqlTsVector and searching, and actually found it to be pretty straight forward. I did encounter two problems, and I'm not sure how I should actually handle it.
-
If I had a pre-existing entity, and I added say the
SearchVectorproperty ofNpgsqlTsVectortype, and I also added fields to be included in that migration, it seemed like the order with which it tried to apply the migrations was backwards... like the setup of the fields to be included in the TsVector, should be last. It was trying to reference columns that were a part of the same migration, but had yet to be created when trying to apply changes related to the creation of that vector and triggers (if that's how that vector gets populated). (I believe I was able to manually open the migration cs, and re-arrange things and then the migration would run.) -
If I have an entity with a predefined vector, and I added a field, and then wanted to update the vector to also reference this field, it seems like the migration is created no problem, but when trying to apply the migration I get an error:
42P17: generation expression is not immutable
I think I understand what that is saying, and I think I understand why, but is there a migration path there even if I have to handle that migration more manually?
- 主要语言
- C#
- 星标
- 1.8k
- 派生
- 268
- 平均合并
- 2 小时 35 分钟
- 30 天内合并 PR
- 136
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
npgsql/efcore.pg 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
NTS: the M ordinate is dropped from geometry SQL literals and from geometries stored in JSON可能已有人在做 @Ahmed7991 于 5 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 85/100
npgsql/efcore.pg#4093 · 1 条评论 ·
维护者通常 1 天内回复
-
`TimeSpan`/`Duration` component members: negative values are floored, and intervals computed in SQL are read field by field可能已有人在做 @jeremy-morren 于 11 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复
-
Numeric storage parameters are formatted with the current culture, so migrations emit 0,01 instead of 0.01可能已有人在做 @Sorbitol 于 12 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 30/100
维护者通常 1 天内回复
-
`Contains` on a JSON primitive collection compares JSON text, so `DateTime` and `TimeOnly` items never match可能已有人在做 @Mr444-dev 于 7 天前认领。 未关闭
难度 4/5 3-5 天 新手友好度 45/100
npgsql/efcore.pg#4099 · 1 条评论 ·
维护者通常 1 天内回复
相似的 Issue
-
Issue-Bug Needs-Triage
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
JiaFeiMiao-K-Cat/DiscImageStudio#281 ·
维护者通常 1 天内回复
-
area/access-management Frontend onboarding candidate :handshake:
难度 2/5 1-3 小时 新手友好度 65/100
Altinn/altinn-auth#4941 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
aws/aws-sdk-net#4586 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
Kryptos-FR/MarkView.Avalonia#269 · 1 个 reaction ·
维护者通常 1 天内回复