Bug #6370 | concat return NULL when it shouldn't? | ||
---|---|---|---|
Submitted: | 1 Nov 2004 19:48 | Modified: | 1 Nov 2004 22:12 |
Reporter: | Min Xu | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: MyISAM storage engine | Severity: | S2 (Serious) |
Version: | 4.0.21 | OS: | Linux (linux tao 1.0) |
Assigned to: | CPU Architecture: | Any |
[1 Nov 2004 19:48]
Min Xu
[1 Nov 2004 20:49]
Min Xu
A more repeatable test case: create table bug_test ( id int, bigdata longblob ); insert into bug_test values (1, "test"); update bug_test set bigdata=concat(bigdata, space(1000000)) where id=1; select length(bigdata) from bug_test; update bug_test set bigdata=concat(bigdata, space(100000)) where id=1; select length(bigdata) from bug_test;
[1 Nov 2004 21:43]
MySQL Verification Team
What is the value of max_allowed_packet variable?
[1 Nov 2004 21:49]
Min Xu
It is more than 200K I think. I could insert a longblob that is bigger than 200K. But not with concat function.
[1 Nov 2004 21:52]
MySQL Verification Team
max_allowed_packet is 1M by default. Check if you exceed this limit.
[1 Nov 2004 22:03]
Min Xu
Thanks, it is working. This really should have print a error msg instead of silently set the field to NULL. Thanks again!