boluor opened a new pull request, #3790:
URL: https://github.com/apache/doris-website/pull/3790

   ## Summary
   
   Doc page (4.x): \`scalar-functions/string-functions/replace-empty.md\` (EN).
   
   Brings the EN page up to the level of the ZH page that already exists:
   
   1. The EN page's first example was \`SELECT replace('hello world', 'world', 
'universe');\` — that is the regular \`REPLACE\` function, not 
\`REPLACE_EMPTY\`. On a page titled REPLACE_EMPTY this is confusing; the prose 
never frames it as a contrast example. Removed.
   2. Added two missing examples that the ZH page already has: NULL 
propagation, and multi-byte (\`ṭṛìṭ\`) \`<new>\`. These are the corner cases 
readers most often look up.
   3. Added the missing \"if \`<old>\` is not in \`<str>\`, returns \`<str>\` 
unchanged\" line to the Return Value spec, and noted the VARCHAR return type.
   4. Reorganized examples as a numbered list with a one-line intro per 
example, matching the ZH page's structure.
   
   ## Verification
   
   Every SQL example was run against a single-node Apache Doris 4.1.1 cluster 
using the actual mysql/mariadb client; the result blocks in this PR are the 
verbatim CLI output (including the wider padding MariaDB emits on the UTF-8 
row, which I matched character-for-character).
   
   ## Test plan
   
   - [x] Run each example in the EN page on a 4.1.1 cluster — all 5 match the 
result blocks exactly.
   - [x] Confirm \`REPLACE_EMPTY\` behavior is unchanged; only the doc 
text/examples are updated.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to