boluor opened a new pull request, #3806:
URL: https://github.com/apache/doris-website/pull/3806
## Summary
Doc page (4.x): \`scalar-functions/date-time-functions/milliseconds-add.md\`
(ZH).
The ZH page included an \"overflow\" example claiming that passing
\`2147483648\` (INT_MAX + 1) as the delta argument returns NULL:
\`\`\`
---delta 参数超过 INT 范围，返回 NULL
SELECT MILLISECONDS_ADD('2023-09-08 16:02:08.435', 2147483648) AS after_add;
+-----------+
| after_add |
+-----------+
| NULL |
+-----------+
\`\`\`
On Apache Doris 4.1.1 the cluster handles this fine because the delta
argument is already \`BIGINT\`:
\`\`\`
SELECT MILLISECONDS_ADD('2023-09-08 16:02:08.435', 2147483648);
-> 2023-10-03 12:33:32.083000
\`\`\`
Update the prose to describe the actual behavior (\"delta supports BIGINT
range; values beyond INT max still compute normally\") and replace the result
block with the real cluster output. No EN-side change because the EN page
didn't include this overflow example.
## Verification
Ran the SELECT plus a few neighboring values (\`2147483647\`,
\`9999999999999\`) on a single-node Apache Doris 4.1.1 cluster — none of them
return NULL; they all compute the future datetime as expected.
## Test plan
- [x] Run the corrected SQL on a 4.1.1 cluster — matches the new result
block.
- [x] Surrounding examples unchanged.
🤖 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]
