[Bug?] Performing SUM function on integer column returns BigDecimal result about trilogy HOT 4 CLOSED

Casting to an Integer when SUMming int columns makes sense to me. I don't think it's too difficult (we already get back information about whether the column includes decimals). I can open a PR later today.

from trilogy.

Awesome, thanks Daniel! 🙏 ❤️

from trilogy.

I'm wondering if this is a bug, or if I'm just missing a query option to cast the result to an Integer properly. At Shopify we're using Sorbet, and it complains loudly if a query ends up returning a BigDecimal when it was expecting an Integer.

Fwiw, this is part of how MySQL itself functions. A SUM() also on integer types always casts to DECIMAL since there's no guarantee otherwise that the result fits. A SUM over bigint columns could easily overflow a bigint.

This is different from COUNT for example which returns a bigint since that's also the maximum number of rows. Also see https://dev.mysql.com/doc/refman/8.0/en/aggregate-functions.html.

I'd argue to be honest here that Sorbet is wrong here. It should expect a DECIMAL like type for a SUM query and not really an integer. Anyway, the ship here probably long ago sailed on these changes.

from trilogy.

I vaguely recall wanting to do this to match what the mysql2 gem does, to make it easier for folks switching over from that gem. We decided against making this change at GitHub and made it configurable in #60, in case that is helpful.

from trilogy.