Skip to content

[fix](doc) zh random.md upper-bound text and bitwise OR cell rendering#3756

Merged
morningman merged 1 commit into
apache:masterfrom
boluor:fix-zh-numeric-bitwise-docs
May 24, 2026
Merged

[fix](doc) zh random.md upper-bound text and bitwise OR cell rendering#3756
morningman merged 1 commit into
apache:masterfrom
boluor:fix-zh-numeric-bitwise-docs

Conversation

@boluor
Copy link
Copy Markdown
Contributor

@boluor boluor commented May 23, 2026

Summary

Two unrelated but small fixes:

  1. `numeric-functions/random.md` (zh) — `` parameter description read "随机数的上限 必须小于下限" (upper bound must be less than lower bound), which is backwards. Corrected to "必须大于下限" across zh current / 2.1 / 3.x / 4.x.
  2. `basic-element/operators/bitwise-operators.md` (EN + zh) — the OR-row example `SELECT 1 | 2` had a literal `|` inside an inline-code cell, which the Docusaurus table renderer truncates to SELECT 1 (visible on the live site). Escape the pipe with `|` so it renders as `SELECT 1 | 2`. Applied to all 8 maintained-version files.

Fixes #2464
Fixes #2463

…endering

- `numeric-functions/random.md` (zh, current / 2.1 / 3.x / 4.x): the `<b>`
  parameter description read "随机数的上限 必须小于下限" — the upper bound
  must be GREATER than the lower bound. Corrected to "必须大于下限".
- `basic-element/operators/bitwise-operators.md` (EN + zh, all maintained
  versions): the `SELECT 1 | 2` example in the OR row contained a literal
  pipe inside an inline-code cell, which Docusaurus' table renderer truncates
  to ``SELECT 1`` (visible at /zh-CN/docs/3.0/sql-manual/basic-element/operators/bitwise-operators).
  Escape the pipe with `&apache#124;` so the cell renders as `SELECT 1 | 2`.

Fixes apache#2464
Fixes apache#2463

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@morningman morningman merged commit fd2f708 into apache:master May 24, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Issue on docs Issue on docs

2 participants