peterjohnlawrence / com.inova8.odata2sparql.v4

Part of the overall odata2sparql solution, this odata2sparql.v4 module containing the olingo4 dependencies. In other words specifically for odata v4
http://inova8.com/bg_inova8.com/offerings/odata2sparql/
Apache License 2.0
5 stars 5 forks source link

Need the ability to define the primary key of an operation entity sometimes rather than allowing it to be deduced from navigation properties #184

Closed peterjohnlawrence closed 4 years ago

peterjohnlawrence commented 4 years ago

getOrCreateOperationNavigationProperty assumes that if it is a navigation property then it will be part of the primary key for the operation. Instead we want to allow specification of which fields are really part of the pseudo primary key:

?If there is a 'allows null' on a navigation property then this could be excluded from key ?Specific navigation properties could be defined as being part of the key, therefore excluding the rest. ?Assume that all navigation properties are nullable except those that are specifically defined as such, however this will require changing all existing operations and also difficult to express nullability with an owl:restriction