(calcite-site) branch main updated: Website deployed from calcite@d59871d49cba28096b698efda80957ecc9e8c4ab

[as...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

asf-ci-deploy pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/calcite-site.git


The following commit(s) were added to refs/heads/main by this push:
     new 42cd37c32 Website deployed from calcite@d59871d49cba28096b698efda80957ecc9e8c4ab
42cd37c32 is described below

commit 42cd37c3287b9b0da008bd9a0c54ae27e0c4f51a
Author: julianhyde <ju...@users.noreply.github.com>
AuthorDate: Sat Oct 5 02:03:06 2024 +0000

    Website deployed from calcite@d59871d49cba28096b698efda80957ecc9e8c4ab
---
 docs/history.html | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/docs/history.html b/docs/history.html
index 0e20e333d..d6e441860 100644
--- a/docs/history.html
+++ b/docs/history.html
@@ -103,6 +103,28 @@ using JDK/OpenJDK versions 8 to 19;
 Guava versions 21.0 to 32.1.3-jre;
 other software versions as specified in gradle.properties.
 
+* [a <href="https://issues.apache.org/jira/browse/CALCITE-2067">]
+  **RexLiteral cannot represent accurately floating point values,
+  including NaN, Infinity**.  This fix changes the way RexLiteral
+  represents floating point values.  Previously floating point values
+  were encoded into BigDecimal values.  This caused precision loss
+  when representing the results of simplifying expressions whose
+  results are floating point.  With this change RexLiteral uses
+  internally a Java Double value to represent a SQL DOUBLE, FLOAT, or
+  REAL value.  The result of RexLiteral.getValue() accordingly changes
+  type in this case.
+
+*Deprecated methods in `interface RelDataTypeSystem`*.
+[<a href="https://issues.apache.org/jira/browse/CALCITE-6598">CALCITE-6598</a>]
+deprecates methods `getMaxNumericScale()` and `getMaxNumericPrecision()`,
+to be consistent with `getMinScale(SqlTypeName)` added in
+[<a href="https://issues.apache.org/jira/browse/CALCITE-6560">CALCITE-6560</a>].
+From 1.38, you should instead call `getMaxScale(DECIMAL)` and
+`getMaxPrecision(DECIMAL)`. If you have overridden these methods, Calcite will
+continue to call your overriding method in 1.38 but will cease in 1.39.
+To avoid this *breaking change in 1.39*, during 1.38 you should move your
+override logic to the `getMaxScale` and `getMaxPrecision` methods.
+
 #### New features
 {: #new-features-1-38-0}