pingcap/tidb

The update statement reported the truncate error message isn’t compatible with MySQL after column type change

Open

#24,642 opened on May 13, 2021

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (6,186 forks)batch import
help wantedseverity/moderatesig/sql-infratype/bug

Repository metrics

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

Description

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

create table t(a char(250) CHARACTER SET utf8);
insert into t set a="";
alter table t modify a char(120) charset binary;
update t set a = 1624877308284165695 where a = 6130350361147116967;

2. What did you expect to see? (Required)

ERROR 1292 (22007): Truncated incorrect DOUBLE value: '0123456789abc\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x0'

3. What did you see instead (Required)

ERROR 1292 (22007): Truncated incorrect FLOAT value: ''

4. What is your TiDB version? (Required)

Release Version: v4.0.0-beta.2-2889-gaa3e64d08 Edition: Community Git Commit Hash: aa3e64d08bf19c7230cc3b53c3a57f68a50ae3c3 Git Branch: master

Contributor guide