perform checks based on NavigationProperty multiplicity #117
Labels
enhancement
New feature or request
Comments
mamiksik
added a commit
to mamiksik/python-pyodata
that referenced
this issue
Jul 16, 2020
Change test entity from Car to Customer, since car can only have one navigation property. A check for correct multiplicity is needed As described in SAP#117.
mamiksik
added a commit
to mamiksik/python-pyodata
that referenced
this issue
Jul 22, 2020
Change test entity from Car to Customer, since car can only have one navigation property. A check for correct multiplicity is needed As described in SAP#117.
filak-sap
pushed a commit
that referenced
this issue
Jul 22, 2020
Change test entity from Car to Customer, since car can only have one navigation property. A check for correct multiplicity is needed As described in #117.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When creating a new entity, it is possible to call the method
setwith an invalid value for a navigation property because the method set does not verify multiplicity of the corresponding navigation property relation ship. To put it simple, it is possible to assign a list to a navigation property which is supposed to be an entity.More explicitly, we need to add a check for multiplicity before the following line:
https://github.com/SAP/python-pyodata/blob/master/pyodata/v2/service.py#L489
The text was updated successfully, but these errors were encountered: