Undeprecate Common.SecondaryKey
#343
Conversation
| @@ -218,15 +218,12 @@ | |||
| </Term> | |||
|
|
|||
| <Term Name="SecondaryKey" AppliesTo="EntityType" Type="Collection(Edm.PropertyPath)" Nullable="false"> | |||
There was a problem hiding this comment.
One of our colleagues mentioned that it would make sense in course of this de-deprecation to call the term SecondaryKeys as it's a collection (analogous to AlternateKeys from the Core vocabulary.
There was a problem hiding this comment.
No, this is a single secondary key with one or more key properties - we do have lots of multi-part keys at SAP.
Multiple secondary keys are differentiated via qualifiers.
vocabularies/Common.xml
Outdated
| <Annotation Term="Core.LongDescription"> | ||
| <String>Multiple secondary keys are possible using different qualifiers. | ||
| Unlike [`Core.AlternateKeys`](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#AlternateKeys), | ||
| secondary keys cannot be used to address an entity in a resource path.</String> |
There was a problem hiding this comment.
I would phrase it a bit weaker ... in a sense that this addressing is not required (but I wouldn't mind if we go with your proposal)
| @@ -218,15 +218,12 @@ | |||
| </Term> | |||
|
|
|||
| <Term Name="SecondaryKey" AppliesTo="EntityType" Type="Collection(Edm.PropertyPath)" Nullable="false"> | |||
There was a problem hiding this comment.
No, this is a single secondary key with one or more key properties - we do have lots of multi-part keys at SAP.
Multiple secondary keys are differentiated via qualifiers.
No description provided.