MySQL Bugs: #23929: prepared statement INSERT into char field, bound to MYSQL_TYPE

Bug #23929	prepared statement INSERT into char field, bound to MYSQL_TYPE_LONG = bad data
Submitted:	3 Nov 2006 10:15	Modified:	6 Aug 2007 14:27
Reporter:	Magnus Blåudd	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Server: Prepared statements	Severity:	S3 (Non-critical)
Version:	4.1.23	OS:	Any
Assigned to:	Konstantin Osipov	CPU Architecture:	Any

Description:
mysql_client_test              [ fail ]

Errors are (from /data0/pushbuild/pb/mysql-4.1-maint/66/mysql-4.1.23-pb66/mysql-test/var/log/mysqltest-time) :
sh: line 1:  3411 Aborted                 /data0/pushbuild/pb/mysql-4.1-maint/66/mysql-4.1.23-pb66/tests/mysql_client_test --no-defaults --testcase --user=root --port=11300 --socket=/dev/shm/pbtmp-n_stm-130/master.sock --getopt-ll-test=25600M >>/data0/pushbuild/pb/mysql-4.1-maint/66/mysql-4.1.23-pb66/mysql-test/var/log/mysql_client_test.log 2>&1
mysqltest: At line 12: command "$MYSQL_CLIENT_TEST --getopt-ll-test=25600M >> $MYSQLTEST_VARDIR/log/mysql_client_test.log 2>&1" failed
(the last lines may be the most important ones)

Stopping All Servers
Restoring snapshot of databases
Resuming Tests

How to repeat:
Compile as PushBuild does on sapsrv2, run ./mysql-test-run.pl --do-test=mysql_client_test

Suggested fix:
I looked at the problem and wrong data is returned in one of the testcases of mysql_client_test thus it aborts. Lost the results

This blocks 4.1-engines from being pushed to main. See https://intranet.mysql.com/~knielsen/pb/getlog.pl?dir=mysql-4.1-engines&entry=istruewing@c...