Bug #37804 falcon_bug_23189 fails on Windows 2003
Submitted: 2 Jul 2008 11:12 Modified: 18 Jul 2008 8:41
Reporter: Hakan Küçükyılmaz Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Falcon storage engine Severity:S2 (Serious)
Version:6.0 OS:Windows (2003 Win64)
Assigned to: Assigned Account CPU Architecture:Any

[2 Jul 2008 11:12] Hakan Küçükyılmaz
Description:
falcon_bug_23189 fails on Windows 2003 on Pushbuild 'vm-win2003-64-b' Win64 VS2005 -max-nt.

How to repeat:
See https://intranet.mysql.com/secure/pushbuild/getlog.pl?dir=bzr_mysql-6.0-falcon&entry=Hakan...

falcon.falcon_bug_23189        [ fail ]

mysqltest: At line 21: query 'DROP TABLE t1' failed: 2013: Lost connection to MySQL server during query

The result from queries just before the failure was:
SET STORAGE_ENGINE = Falcon;
*** Bug #23189 ***
DROP TABLE IF EXISTS t1;
DROP TABLE IF EXISTS t2;
CREATE TABLE t1 (a varchar(1100));
INSERT INTO t1 VALUES (repeat('r',1100));
CREATE INDEX i ON t1 (a);
CREATE TABLE t2 (a varchar(20000));
INSERT INTO t2 VALUES (repeat('r',20000));
CREATE INDEX i ON t2 (a);
Warnings:
Warning	1071	Specified key was too long; max key length is 1100 bytes
Warning	1071	Specified key was too long; max key length is 1100 bytes
Warning	1071	Specified key was too long; max key length is 1100 bytes
DROP TABLE t1;

More results from queries before failure can be found in e:\var-falcon-102\log\falcon_bug_23189.log

Stopping All Servers
mtr_ping_with_timeout(): At least one server is alive.
mysql-test-run: WARNING: Forcing kill of process 2352
Restoring snapshot of databases
Resuming Tests
[18 Jul 2008 8:41] Hakan Küçükyılmaz
This is the same problem as in Bug#35072.