SQlite caching layer appends a ".0" to BigDecimal fields that happen to be integers
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 8
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
This changes equality comparisons in tests, but we have no evidence or reason to believe this poses any risk to nominal use. This can be exercised by changing mmtc-core/src/test/resources/TimeCorrelationConfigProperties.xml key telemetry.source.plugin.rawTlmTable.readDownlinkDataRate to true and running TelemetryCacheTest.simpleTest.
fysa @Lagejohn
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
Start with mmtc-core/src/test/resources/TimeCorrelationConfigProperties.xml and enable the readDownlinkDataRate key, then run TelemetryCacheTest.simpleTest to reproduce the changed equality comparison. Trace the SQLite caching path used by that test and verify that integer-valued BigDecimal fields are no longer returned with an appended ".0".
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, sqlite
- Domain
- database
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100