blob/text/int length isn't accuracy in column metadata · pingcap/tidb#7465

2018-08-22T12:45:04.000Z

1. What did you do? connection tidb with `--column-type-info` ``` create table bitest(b blob(2)); select * from bitest; ``` 2. What did you expect to see? ``` Length: 255 ``` 3. What did you see instead? ``` Length: 8 ``` 4. What version of TiDB are you using (`tidb-server -V` or run `select tidb_version();` on TiDB)? ``` 2.0.6 ``` ref #7463

(2 留言) (0 反應) (0 負責人)Go (40,090 star) (6,186 fork)batch import

help wantedtype/compatibility

描述

What did you do?

connection tidb with --column-type-info

create table bitest(b blob(2));
select * from bitest;

What did you expect to see?

Length:     255

What did you see instead?

Length:     8

What version of TiDB are you using (tidb-server -V or run select tidb_version(); on TiDB)?

2.0.6

ref #7463

貢獻者指南

技術棧: gosql
領域: databasebackend
議題類型: bug
難度: 3
預計時間: half day
活動狀態: stale
清晰度: mostly clear
前置要求: Go programmingTiDB internals
新手友善度: 40
研究方向: Investigate how TiDB reports column length for blob/text types. Compare the expected length (255 for blob(2)) with actual (8). The issue references #7463, which may contain related context. Look at the server's column metadata handling, possibly in the session or protocol layer.