On Fri, 08 Oct 2021 08:47:33 -0400 "David Li" <lidav...@apache.org> wrote: > At max precision, we currently error out regardless of scale. > > It looks like SQL Server not only saturates at max precision, but may also > reduce scale. I think we can provide that as an option if there's demand for > it. But we can at least promote decimal128 to decimal256 and perform overflow > checks.
I am not sure if promotion to decimal256 is something we want to do automatically (we don't promote int32 to int64 automatically, for example). Regards Antoine.
