pingcap/tidb

Make a case for supporting other characters, such as the GB 18030 character set

Open

#31,688 opened on Jan 14, 2022

View on GitHub
 (0 comments) (1 reaction) (1 assignee)Go (6,186 forks)batch import
help wantedtype/feature-request

Repository metrics

Stars
 (40,090 stars)
PR merge metrics
 (Avg merge 14d 4h) (346 merged PRs in 30d)

Description

  • #31690
  • #31692
  • Support gb18030_bin collation
    • #31693
    • Support gb18030_bin collation in Coprocessor
  • Support gb18030_chinese_ci collation
    • #31694
    • Support gb18030_chinese_ci collation in Coprocessor

Support gb18030_unicode_520_ci sort (currently not required)

Contributor guide

Research direction
Study the existing collation implementations in the coprocessor module, particularly for other character sets like utf8mb4. Identify the pattern for adding a new collation (e.g., gb18030 bin and gb18030 chinese ci) and implement the necessary logic in the coprocessor to handle the new collation. Ensure that the collation is registered and integrated with the existing framework.
Tech stack
go
Domain
database
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoDatabase collation knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60