[Bug]: Table writes fail (HTTP 500) for entities defined in a linked `data-source-files` config
维护者通常 1 天内回复
@souvikghosh04 已经在做这个了。
开始于 2026年7月7日。
评估
这个 Issue 还没有评估数据。
描述
When
Using a multi-database setup where a root config links a second database config via data-source-files:
# Root config (database 1)
dab init --database-type mssql --connection-string "@env('DAB_SQL_DB1')" --host-mode Development -c dab-config.json
dab add Db1Orders --source dbo.Orders --permissions "anonymous:*" --source.type table -c dab-config.json
# Linked config (database 2)
dab init --database-type mssql --connection-string "@env('DAB_SQL_DB2')" --host-mode Development -c dab-config-db2.json
dab add Db2Customers --source dbo.Customers --permissions "anonymous:*" --source.type table -c dab-config-db2.json
# Link them
dab configure --data-source-files dab-config-db2.json -c dab-config.json
dab start -c dab-config.json
Then send a write to a table entity that is defined in the linked file (dab-config-db2.json):
POST /api/Db2Customers
Content-Type: application/json
{ "Name": "test" }
Expected
The insert succeeds and returns HTTP 201 with the created row, the same as an equivalent table entity defined in the root config. Table writes should work regardless of whether the entity's data source is in the root config or in a linked data-source-files config.
Actual
The request returns HTTP 500 with a generic error:
{
"error": {
"code": "UnexpectedError",
"message": "While processing your request the server ran into an unexpected error.",
"status": 500
}
}
The server log shows a KeyNotFoundException keyed by the entity name, thrown in the SQL mutation/insert path:
System.Collections.Generic.KeyNotFoundException: The given key 'Db2Customers' was not present in the dictionary.
at Azure.DataApiBuilder.Core.Resolvers.BaseQueryStructure..ctor(...)
at Azure.DataApiBuilder.Core.Resolvers.SqlInsertStructure..ctor(...)
at Azure.DataApiBuilder.Core.Resolvers.SqlMutationEngine.PerformMutationOperation(...)
Scope / Root cause (confirmed by test)
The failure is positional, not database- or table-specific. Swapping the topology proves it — the same table behaves differently based only on which config file it lives in:
| Table | In root config | In linked data-source-files config |
|---|---|---|
dbo.Categories |
POST succeeds (200/201) | POST fails (500) |
dbo.Category |
POST succeeds (200/201) | POST fails (500) |
Additional observations:
- Reads (
GET) work for linked-file entities. - Stored procedures in linked files work (they use the
executepath, not the table-mutation path). - Only table mutations (
POST/PUT/PATCH/DELETE) on linked-file entities fail. dab validatepasses and reports REST paths for all entities across both files.
Impact
In a multi-database DAB instance, tables in any linked (non-root) database are effectively read-only. Only the root database supports table writes.
- 主要语言
- C#
- 星标
- 1.5k
- 派生
- 372
- 平均合并
- 9 天 2 小时
- 30 天内合并 PR
- 10
环境准备
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Azure/data-api-builder 的其他 Issue
-
pgsql
难度 2/5 1-3 小时 新手友好度 68/100
Azure/data-api-builder#3598 ·
维护者通常 1 天内回复
-
2.x cli mcp-server
难度 2/5 1-3 小时 新手友好度 68/100
Azure/data-api-builder#3576 ·
维护者通常 1 天内回复
-
2.x health-endpoint
难度 2/5 1-3 小时 新手友好度 68/100
Azure/data-api-builder#3570 ·
维护者通常 1 天内回复
-
2.x telemetry
难度 2/5 1-3 小时 新手友好度 68/100
Azure/data-api-builder#3564 ·
维护者通常 1 天内回复
-
2.x telemetry
难度 2/5 1-3 小时 新手友好度 70/100
Azure/data-api-builder#3562 ·
维护者通常 1 天内回复
查看 Azure/data-api-builder 的全部 Issue
相似的 Issue
-
area-System.Numerics.Tensors untriaged
难度 2/5 1-3 小时 新手友好度 78/100
dotnet/runtime#134691 · 2 条评论 ·
维护者通常 1 天内回复
-
ci-failure-cause test-failure
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 2/5 1-3 小时 新手友好度 78/100
AvaloniaUI/Avalonia#22312 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 68/100