pingcap/tidb

ERROR 1305 (42000): FUNCTION UUID_SHORT does not exist

Open

#4,620 建立於 2017年9月25日

在 GitHub 查看
 (13 留言) (0 反應) (0 負責人)Go (40,090 star) (6,186 fork)batch import
component/expressiongood first issuehelp wanted

描述

Please answer these questions before submitting your issue. Thanks!

  1. What did you do? If possible, provide a recipe for reproducing the error.

SELECT UUID_SHORT();

  1. What did you expect to see?

+-------------------+ | UUID_SHORT() | +-------------------+ | 97316296756035585 | +-------------------+ 1 row in set (0.00 sec)

  1. What did you see instead?

ERROR 1305 (42000): FUNCTION UUID_SHORT does not exist

  1. What version of TiDB are you using (tidb-server -V)?

Release Version: 0.9.0 Git Commit Hash: fa87ec45a9acf93fc6e740ecb617b4a100d0d867 Git Commit Branch: HEAD UTC Build Time: 2017-09-24 01:38:26

貢獻者指南

技術棧
gosql
領域
databasebackend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Go programmingTiDB internalsSQL function implementation
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
The issue requests implementing the MySQL UUID SHORT() function. To start, examine how other built in functions like UUID() are implemented in the TiDB codebase. Look at files in the expression package (e.g., builtin uuid.go) for registration and evaluation logic. Ensure to add the function to the builtin list and handle cross version compatibility if needed. The discussion in the issue comments may provide additional context on expected behavior.