[IGNITE-23172] Sql. Lack of bounds validation in CAST(1 as DECIMAL(MAX_PREC, MAX_SCALE))

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: sql
• Labels: ignite-3
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Konstantin Orlov
• Reporter: Konstantin Orlov
• Created: 09/Sep/24 12:00
• Updated: 16/Oct/24 14:54
• Resolved: 16/Oct/24 14:54

Description

A query like SELECT CAST(1 AS DECIMAL(32767, 32767)) returns 1 although it must throw Numeric field overflow.

Let's fix validation during CAST when precision and scale equals to their max values.

Issue Links

• is related to: IGNITE-23463 Document changes in type derivation for BigDecimal dynamic params
• links to: GitHub Pull Request #4566