News
I am upgrading from spring-data-mongodb 3.2.3 to 3.3.1, and also to Java 17. Here is a test that worked before: EDIT: this seems to be a Java 17 problem, the same issue exists in Spring Data Mongo 3.2 ...
Not all Java developers need the precision that BigDecimal offers. However, those who do usually don’t have to use BigDecimal for very long before running into the java.lang.ArithmeticException ...
When azure-spring-data-cosmos serializes an entity with a BigDecimal field trailing zeros in the decimal portion are lost thus ignoring the scale. For example, 43769.30 is serialized as 43769.3.
Some results have been hidden because they may be inaccessible to you
Show inaccessible results