pingcap/tidb

Built-in function SOUNDEX not supported

Open

#3,930 建立於 2017年7月28日

在 GitHub 查看
 (4 留言) (0 反應) (0 負責人)Go (40,090 star) (6,186 fork)batch import
component/expressionhelp wantedtype/compatibility

描述

Please answer these questions before submitting your issue. Thanks!

  1. What did you do?
create table t1 (id integer, a varchar(100) character set utf8 collate utf8_unicode_ci); 
insert into t1 values (1, 'Test');    
select * from t1 where soundex(a) = soundex('Test');
  1. What did you expect to see?
+------+------+
| id   | a    |
+------+------+
|    1 | Test |
+------+------+
1 row in set (0.01 sec)
  1. What did you see instead?
ERROR 1105 (HY000): line 0 column 31 near "a) = soundex('Test')" (total length 51)
  1. What version of TiDB are you using (tidb-server -V)?

貢獻者指南

技術棧
go
領域
database
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
basic Go knowledgeunderstanding of TiDB expression layer
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
First, identify where built in functions are registered in TiDB. The expression package likely has a file like 'builtin string.go' where string functions are implemented. Look for existing similar functions (e.g., SOUNDEX is a string function). The implementation needs to compute the Soundex code (e.g., using a hash or algorithm as per MySQL standard). Also, add the function to the function registry and ensure it appears in MySQL compatibility tests. Check the issue comments for any additional context or prior attempts.