Update docs for expression defaults #19685
Conversation
ti-chi-bot
bot
added
missing-translation-status
|
@CbcWestwolf: adding LGTM is restricted to approvers and reviewers in OWNERS files. In response to this: Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
hfxsd
added
translation/done
| @@ -46,9 +46,48 @@ Starting from v8.0.0, TiDB additionally supports specifying the following expres | |||
| * `DATE_FORMAT(NOW(), '%Y-%m-%d %H.%i.%s')` | |||
| * `DATE_FORMAT(NOW(), '%Y-%m-%d %H:%i:%s')` | |||
| * `STR_TO_DATE('1980-01-01', '%Y-%m-%d')` | |||
| * [`CURRENT_TIMESTAMP()`](/functions-and-operators/date-and-time-functions.md), [`CURRENT_DATE()`](/functions-and-operators/date-and-time-functions.md): both with default fsp | |||
There was a problem hiding this comment.
| * [`CURRENT_TIMESTAMP()`](/functions-and-operators/date-and-time-functions.md), [`CURRENT_DATE()`](/functions-and-operators/date-and-time-functions.md): both with default fsp | |
| * [`CURRENT_TIMESTAMP()`](/functions-and-operators/date-and-time-functions.md), [`CURRENT_DATE()`](/functions-and-operators/date-and-time-functions.md): both use the default fsp (fractional seconds precision) |
Co-authored-by: xixirangrang <[email protected]>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What is changed, added or deleted? (Required)
Use https://github.com/pingcap/tidb/blob/5e8d1b8ae1de446841c105d0c177320c88ff893d/pkg/ddl/add_column.go#L628-L787 to update the docs
See also:
rand()as column default value tidb#32608Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?