Enrich Documentation: TiDB String Functions

[qiancai]

Overview

The current document for TiDB's string functions provides basic information for each supported function without detailed descriptions and examples. To make this document more comprehensive and user-friendly, we welcome external contributors to enrich the instructions for each string function.

Objectives

• Enhance the document for TiDB's string functions by providing detailed instructions and examples for each function.
• Ensure consistency and clarity in this document.

Required skills

• Proficiency in SQL and TiDB string functions.

Contribution guidelines

1. Choose two string functions from the list of sub-issues.
2. Go to the sub-issue link of these two string functions.
3. Assign the issue to yourself by commenting /assign.
4. Submit a pull request (PR) to the TiDB docs repositories (either pingcap/docs in English or pingcap/docs-cn in Chinese, or both).
5. In the PR description, indicate which sub-issue this PR resolves, such as "Fix #xxx".

List of sub-issues

Note: Except for the first 11 lines, the other lines in the following list are not issues yet. We'll convert them to sub-issues after the 11 issues are assigned. If you want to enrich instructions for certain string functions that are not sub-issues yet, please add a comment on this issue.

• Enrich instructions for string functions ASCII() and BIN() #15418
• Enrich instructions for string functions BIT_LENGTH() and CHAR() #15482
• Enrich instructions for string functions CHAR_LENGTH() and CHARACTER_LENGTH() #15483
• Enrich instructions for string functions CONCAT() and CONCAT_WS() #15484
• Enrich instructions for string functions ELT() and EXPORT_SET() #15485
• Enrich instructions for string functions FIELD() and FIND_IN_SET() #15486
• Enrich instructions for string functions FORMAT() and FROM_BASE64() #15487
• Enrich instructions for string functions HEX() and INSERT() #15488
• Enrich instructions for string functions INSTR() and LCASE() #15489
• Enrich instructions for string functions LEFT() and LENGTH() #15491
• Enrich instructions for string functions LIKE and LOCATE() #15490
• Enrich instructions for string functions LOWER() and LPAD() #16937
• Enrich instructions for string functions LTRIM() and MAKE_SET() #16938
• Enrich instructions for string functions MID() and NOT LIKE #16939
• Enrich instructions for string functions NOT REGEXP and OCT() #16940
• Enrich instructions for string functions OCTET_LENGTH() and ORD() #16941
• Enrich instructions for string functions POSITION() and QUOTE() #16942
• Enrich instructions for string functions REGEXP and REGEXP_INSTR() #16943
• Enrich instructions for string functions REGEXP_LIKE() and REGEXP_REPLACE() #16944
• Enrich instructions for string functions REGEXP_SUBSTR() and REPEAT() #16945

Additional information

• To learn how to create a pull request, see TiDB Documentation Contributing Guide.
• Make sure to test your provided instructions in TiDB. To quickly get started with TiDB Cloud or TiDB, check out the following guides:
  • TiDB Cloud Quick Start | PingCAP Docs
  • Quick Start Guide for the TiDB Database Platform | PingCAP Docs
• DO NOT copy instructions from documentation of other databases.

Thank you for contributing to the improvement of TiDB's documentation! If you have any questions, feel free to comment on this issue.

[kjhuang-db]

who can participate in this 文档挑战赛？

[qiancai]

who can participate in this 文档挑战赛？

Anyone interested is welcome to participate in this event. For enriching documentation, you can either create a PR in English at pingcap/docs, or create a PR in Chinese at pingcap/docs-cn, or both.

[dveeden]

Looks like multi argument CHAR() isn't documented yet