Repository navigation

fix: do not evaluate a volatile coalesce or nvl argument twice - #25561

Draft

DeviousCardi wants to merge 5 commits into

apache:mainfrom

DeviousCardi:fix/25477-coalesce-volatile-double-eval

Draft

fix: do not evaluate a volatile coalesce or nvl argument twice#25561
DeviousCardi wants to merge 5 commits into
apache:mainfrom
DeviousCardi:fix/25477-coalesce-volatile-double-eval

Commits on Oct 23, 2026
- fix: do not evaluate a volatile coalesce/nvl argument twice
  
  DeviousCardi
  and
  claude
  committed
  f521c1f
- Only guard the coalesce arguments the rewrite actually duplicates
  
  DeviousCardi
  and
  claude
  committed
  845910e
- Document that a volatile coalesce or nvl argument is evaluated eagerly
  
  DeviousCardi
  and
  claude
  committed
  8b9331b
- test: cover a volatile last coalesce argument that would divide by zero
  
  DeviousCardi
  and
  claude
  committed
  2b794ef
- Format coalesce upgrade note after resolving merge conflict
  DeviousCardi
  committed
  146a3eb