Add page on MySQL commands that are noops in TiDB
Open
Nobody has claimed this yet.
2024-tidb-docs-dash
help wanted
tracked
- Dominant language
- Python
- Stars
- 617
- Forks
- 724
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 223
Description
It might be useful to clarify in one location that some MySQL-isms aren't relevant to TiDB, and so for compatibility just return OK.
For example: FLUSH LOGS, FLUSH HOSTS, etc.
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
The issue names no files, tests, or entry points. Start by reviewing the TiDB documentation structure and verify the behavior of the example commands FLUSH LOGS and FLUSH HOSTS; done means a single page clearly lists the relevant MySQL commands that TiDB accepts as no-ops.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mysql
- Domain
- databases, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100