-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[CALCITE-6598] In RelDataTypeSystem, deprecate methods getMaxNumericS…
…cale and getMaxNumericPrecision You should instead use methods getMaxScale(DECIMAL) and getMaxPrecision(DECIMAL). Because these methods are an SPI (callback), we have to deprecate them in two phases. * In 1.38, the methods are deprecated, to dissuade people from calling them. But some people will have overridden them in their implementation of RelDataTypeSystem, so Calcite will continue to call them. If you have a custom type system, you should move your customizations to the getMaxPrecision(SqlTypeName) and have your getMaxNumericPrecision() call getMaxPrecision(DECIMAL). (Ditto getMaxScale.) * In 1.39, the methods will still be present and deprecated, but Calcite will no longer call them. You should remove all calls to the methods, and all overrides of the methods. * In 2.0, the methods will be removed.
- Loading branch information
1 parent
2ce9ba4
commit d59871d
Showing
14 changed files
with
255 additions
and
60 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.