-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix the descriptions about comment length in table, column, and index #8059
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
Co-authored-by: wjHuang <huangwenjun1997@gmail.com>
Co-authored-by: wjHuang <huangwenjun1997@gmail.com>
@wjhuang2016 @tangenta PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The TiDB PR won't be cherry-picked to 5.3 or 5.4, so this modification only affects the master branch of docs.
@@ -301,6 +301,7 @@ CREATE UNIQUE INDEX c1 ON t1 (c1) INVISIBLE; | |||
* 无法向表中添加 `CLUSTERED` 类型的 `PRIMARY KEY`。要了解关于 `CLUSTERED` 主键的详细信息,请参考[聚簇索引](/clustered-indexes.md)。 | |||
* 表达式索引与视图存在兼容性问题。通过视图进行查询时,无法使用上表达式索引。 | |||
* 表达式索引与 Binding 存在兼容性问题。当表达式索引中的表达式存在常量时,对应查询所建的 Binding 会扩大范围。假设表达式索引中的表达式为 `a+1`,对应的查询条件为 `a+1 > 2`。则建立的 Binding 为 `a+? > ?`,这会导致像 `a+2 > 2` 这样的查询也会强制使用表达式索引,得到一个较差的执行计划。这同样影响 SQL Plan Management (SPM) 中的捕获和演进功能。 | |||
* 索引的 `COMMENT` 属性最多支持 1024 个字符。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is exactly the same with MySQL, so we don't need to declare it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK
@@ -191,7 +191,7 @@ mysql> DESC t1; | |||
* 不支持 `FULLTEXT`,`HASH` 和 `SPATIAL` 索引。 | |||
* 为了与 MySQL 兼容,`index_col_name` 属性支持 length 选项,最大长度默认限制为 3072 字节。此长度限制可以通过配置项 `max-index-length` 更改,具体请参阅 [TiDB 配置文件描述](/tidb-configuration-file.md#max-index-length)。 | |||
* 为了与 MySQL 兼容,TiDB 会解析但忽略 `index_col_name` 属性的 `[ASC | DESC]` 索引排序选项。 | |||
* `COMMENT` 属性最多支持 1024 个字符,不支持 `WITH PARSER` 选项。 | |||
* 表的 `COMMENT` 属性最多支持 2048 个字符;列的 `COMMENT` 属性最多支持 1024 个字符,不支持 `WITH PARSER` 选项。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about the index comment and table partition comment?
I think it's fine to remove the declaration because it now keeps the same with MySQL.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PTAL
@CbcWestwolf: 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 ti-community-infra/tichi repository. |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 85f634f
|
In response to a cherrypick label: new pull request created: #8150. |
First-time contributors' checklist
What is changed, added or deleted? (Required)
The related PR in tidb: pingcap/tidb#30973
Which 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 (in Chinese).
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?