我正在使用Microsoft.OData.Core(等)中的ODataLib v7.1.1位构建OData服务。我在使用ODataUriParser.ParsePath()缩短的键谓词URL格式时遇到了问题。 (相对)URL“Company('Comp1')/ Customer(1)”抛出异常“URI中指定的键数与资源'Test.Customer'的键属性数不匹配”。
模型非常简单,我不明白为什么这不起作用。 URL的其他格式(“公司('Comp1')”,“客户(CompanyId ='COMP1',CustNum = 1)”)。
我已将模型构建器代码与$ metadata输出一起放在下面。任何帮助,将不胜感激。谢谢!
-Erik
var result = new EdmModel();
var company = new EdmEntityType("Test", "Company");
var companyKey1 = company.AddStructuralProperty("CompanyId", EdmPrimitiveTypeKind.String, false);
company.AddKeys(
companyKey1
);
result.AddElement(company);
var customer = new EdmEntityType(NS, "Customer");
var customerKey1 = customer.AddStructuralProperty("CompanyId", EdmPrimitiveTypeKind.String, false);
var customerKey2 = customer.AddStructuralProperty("CustNum", EdmPrimitiveTypeKind.Int32, false);
customer.AddKeys(
customerKey1,
customerKey2
);
result.AddElement(customer);
var navCompanyCustomer = company.AddUnidirectionalNavigation(
new EdmNavigationPropertyInfo()
{
ContainsTarget = true,
Name = "Customer",
Target = customer,
TargetMultiplicity = EdmMultiplicity.Many
});
var customerRefToCompany = customer.AddUnidirectionalNavigation(
new EdmNavigationPropertyInfo()
{
ContainsTarget = false,
Name = "Company",
Target = company,
TargetMultiplicity = EdmMultiplicity.One,
DependentProperties = new[] { customerKey1 },
PrincipalProperties = new[] { companyKey1 }
});
var container = new EdmEntityContainer("Test", "DefaultContainer");
result.AddElement(container);
container.AddEntitySet("Company", company);
container.AddEntitySet("Customer", customer);
return result;
<edmx:Edmx Version="4.0" xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx">
<edmx:DataServices>
<Schema Namespace="Test" xmlns="http://docs.oasis-open.org/odata/ns/edm">
<EntityType Name="Company">
<Key>
<PropertyRef Name="CompanyId" />
</Key>
<Property Name="CompanyId" Type="Edm.String" Nullable="false" />
<NavigationProperty Name="Customer" Type="Collection(Test.Customer)" ContainsTarget="true" />
</EntityType>
<EntityType Name="Customer">
<Key>
<PropertyRef Name="CompanyId" />
<PropertyRef Name="CustNum" />
</Key>
<Property Name="CompanyId" Type="Edm.String" Nullable="false" />
<Property Name="CustNum" Type="Edm.Int32" Nullable="false" />
<NavigationProperty Name="Company" Type="Test.Company" Nullable="false">
<ReferentialConstraint Property="CompanyId" ReferencedProperty="CompanyId" />
</NavigationProperty>
</EntityType>
<EntityContainer Name="DefaultContainer">
<EntitySet Name="Company" EntityType="Test.Company" />
<EntitySet Name="Customer" EntityType="Test.Customer" />
</EntityContainer>
</Schema>
</edmx:DataServices>
</edmx:Edmx>
答案 0 :(得分:0)
我明白了。我将Dependent / Principal属性反转(更正后的代码如下)。其中一个重大争论(多年前)是箭头应该指向实体关系模型中的RI声明(即哪一方依赖)。我一定是在那个失败的一方。 ;)
var navCompanyCustomer = company.AddUnidirectionalNavigation(
new EdmNavigationPropertyInfo()
{
ContainsTarget = true,
Name = "Customer",
Target = customer,
TargetMultiplicity = EdmMultiplicity.Many,
DependentProperties = new[] { companyKey1 },
PrincipalProperties = new[] { customerKey1 }
});