plausible / ecto_ch / dc3ea20d3102b19034350a96ea40c8c599bb7624-PR-271 / 1
88%
master: 88%

LAST BUILD BRANCH: comment-column-option
DEFAULT BRANCH: master
Ran
Files 12
Run time 1s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 87.98% (+0.05%) from 87.928%
dc3ea20d3102b19034350a96ea40c8c599bb7624-PR-271.1

Pull #271

github

ruslandoga 
Bound Decimal rendering to ClickHouse precision limits

The adapter previously emitted Decimal64(scale) for every Decimal parameter regardless of value size and rendered the coefficient with Decimal.to_string/2 verbatim. Both the inline literal path (expr/4) and the parameter type path (param_type/1) are now guarded by a shared decimal_precision_and_scale!/1 helper that:

- rejects non-finite values (NaN, Infinity) with ArgumentError
- rejects scale > 76 with ArgumentError
- rejects coefficients with more than 76 digits with ArgumentError
- rejects computed precision > 76 with ArgumentError

param_type/1 now emits Decimal(precision, scale) sized to the actual value (up to ClickHouse's Decimal256 ceiling of precision 76) instead of always Decimal64(scale). Rendering goes through a new decimal_to_string/1 helper that, when the upstream Decimal library exposes Decimal.to_string/3 with :max_digits, caps output at 77 digits and otherwise falls back to Decimal.to_string/2.

Behavioral change for callers: Decimal parameters and inlined Decimal literals that exceed ClickHouse's Decimal limits, or that are NaN or Infinity, now raise ArgumentError at render time instead of silently producing malformed SQL. No new public option or API surface is added.
Pull Request #271: Bound Decimal rendering to ClickHouse precision limits

893 of 1015 relevant lines covered (87.98%)

662.32 hits per line

Source Files on job dc3ea20d3102b19034350a96ea40c8c599bb7624-PR-271.1