Files
bun.sh/src
Sosuke Suzuki a118c9e636 fix(sql): fix inverted logic in JSC__isBigIntInInt64Range/UInt64Range
The C++ implementation had two compounding bugs:
1. Parameter names were swapped: Zig passes (min, max) but C++ declared (max, min)
2. The logic used OR short-circuit instead of AND, returning true on the first check

Combined, this caused the function to return true when the BigInt was
OUTSIDE the range, and false when it was INSIDE — the exact opposite of
the intended behavior.

Impact:
- All BigInt parameter binding in Bun.SQL (MySQL) would fail with
  ERR_OUT_OF_RANGE for valid in-range values
- Out-of-range BigInts would be silently accepted and truncated

Fix: Change parameter order to (min, max) and use proper AND logic
(return false if < min, otherwise check <= max).

Added regression tests via bun:internal-for-testing that directly
exercise both functions, plus MySQL integration tests for BigInt
parameter binding.
2026-02-26 12:54:19 +09:00
..
2025-11-10 14:38:26 -08:00
2025-11-10 14:38:26 -08:00
2026-02-03 22:18:40 -08:00
2025-11-10 14:38:26 -08:00
2025-11-10 14:38:26 -08:00
2025-11-10 14:38:26 -08:00
2025-11-20 20:56:02 -08:00
2025-11-10 14:38:26 -08:00
2025-11-10 14:38:26 -08:00
2025-12-25 14:00:58 -08:00
2025-11-10 14:38:26 -08:00
2025-10-04 02:17:55 -07:00
2025-11-10 14:38:26 -08:00
2025-11-10 14:38:26 -08:00
2025-11-10 14:38:26 -08:00
2025-11-10 14:38:26 -08:00
2025-11-10 14:38:26 -08:00
2025-11-20 20:56:02 -08:00
2025-11-10 14:38:26 -08:00
2025-11-10 14:38:26 -08:00
2025-11-10 14:38:26 -08:00
2025-11-10 14:38:26 -08:00
2025-11-10 14:38:26 -08:00
2025-11-10 14:38:26 -08:00
2025-09-09 20:41:10 -07:00
2025-11-10 14:38:26 -08:00
2025-11-10 14:38:26 -08:00
2025-11-10 14:38:26 -08:00
2025-11-10 14:38:26 -08:00
2025-11-10 14:38:26 -08:00
2026-01-30 01:38:45 -08:00
2025-12-01 21:59:11 -08:00
2025-11-10 14:38:26 -08:00
2025-11-10 14:38:26 -08:00
2025-11-10 14:38:26 -08:00