Enrich Documentation: Type Conversion in Expression Evaluation
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 617
- Forks
- 724
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 223
Description
Overview
The current Type Conversion in Expression Evaluation document for TiDB only provides a link to the MySQL documentation without any details instructions and examples for TiDB. To make this document more comprehensive and user-friendly, we welcome external contributors to add instructions and examples to this document.
Required skills
Proficiency in SQL and TiDB type conversion in expression evaluation.
Contribution guidelines
- Assign the issue to yourself by commenting
/assign. - Submit a pull request (PR) to the TiDB docs repositories (either pingcap/docs in English or pingcap/docs-cn in Chinese, or both).
- In the PR description, indicate which issue this PR resolves, such as "Fix #15444".
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked TiDB “Type Conversion in Expression Evaluation” document and the referenced MySQL documentation. Confirm TiDB-specific behavior, then add clear instructions and examples to the document; done means the page provides TiDB details rather than only linking to MySQL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- databases, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100