OData / OData/odataorg.github.io
OData V2,V3,V4 reference service's int-decimal problem(s)
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 73
- Forks
- 106
- PR merge metrics
- No merged PRs in 30d
Description
Dear OData group
The reference services for V2,V4 which can be reached may have some inconsistency with the Standards.
http://services.odata.org/V2/(S(readwrite))/OData/OData.svc/
http://services.odata.org/V3/(S(readwrite))/OData/OData.svc/
http://services.odata.org/V4/(S(readwrite))/OData/OData.svc/
In the following cases the service returns numbers with scales(one or two decimals) eg. 5.01
whereas:
OData V2: The Price property in Product entity type is missing Scale="2", so it is treated as an integer property (as per OData specs, omitting scale implies Scale="0").
OData V4: The TotalExpense property in Person entity type is missing Scale="2", so it is treated as an integer property (as per OData specs, omitting scale implies Scale="0").
OData V3:
The TotalExpense property in Person entity type is missing Scale="2", so it is treated as an integer property (as per OData specs, omitting scale implies Scale="0").
Please find attached the corrected (expected) metadata documents for these.
OdataMetadataDocs.zip
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the metadata returned by the linked V2, V3, and V4 reference-service URLs with the corrected documents in OdataMetadataDocs.zip. Check the Price and TotalExpense declarations for the expected Scale="2" behavior, and consider the work done when the services' metadata and returned decimal values agree with the applicable OData standards.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100