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 comments) (0 reactions) (0 assignees)Go (40,090 stars) (6,186 forks)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
Issue 種別: 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.