Skip to content

Commit 146a3eb

Browse files
committed
Format coalesce upgrade note after resolving merge conflict
1 parent 2b794ef commit 146a3eb

1 file changed

Lines changed: 2 additions & 3 deletions

File tree

  • docs/source/library-user-guide/upgrading

‎docs/source/library-user-guide/upgrading/56.0.0.md‎

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1309,8 +1309,7 @@ also accounts for the output ordering.
13091309

13101310
### A volatile `coalesce` or `nvl` argument is now evaluated eagerly
13111311

1312-
`coalesce` and `nvl` are normally rewritten to `CASE WHEN a IS NOT NULL THEN a
1313-
ELSE b END`, which names every argument but the last one twice. For a volatile
1312+
`coalesce` and `nvl` are normally rewritten to `CASE WHEN a IS NOT NULL THEN a ELSE b END`, which names every argument but the last one twice. For a volatile
13141313
argument those two mentions were two independent draws, so
13151314
`coalesce(nullif(floor(random() * 2), 0), -1)` could return `NULL` — a value a
13161315
single evaluation can never produce — or fail at run time with
@@ -1328,7 +1327,7 @@ SELECT coalesce(random(), y / x) FROM t;
13281327
```
13291328

13301329
Only calls that contain a volatile argument before the last one are affected.
1331-
A volatile *last* argument still takes the lazy rewrite, and non-volatile
1330+
A volatile _last_ argument still takes the lazy rewrite, and non-volatile
13321331
`coalesce` and `nvl` are unchanged.
13331332

13341333
To force conditional evaluation, rewrite using `CASE`, which has standardized

0 commit comments

Comments
 (0)