Re: error 127 from table handler with latest mysql 4.0.0 sources. - Sasha Pachev - com.mysql.lists.bugs

20 messages in com.mysql.lists.bugsRe: error 127 from table handler with...

From	Sent On	Attachments
Fournier Jocelyn [Presence-PC]	19 Aug 2001 08:16
Sinisa Milivojevic	20 Aug 2001 03:15
Sinisa Milivojevic	20 Aug 2001 03:20
Michael Widenius	20 Aug 2001 05:27
Fournier Jocelyn [Presence-PC]	20 Aug 2001 09:01
Sinisa Milivojevic	20 Aug 2001 11:31
Fournier Jocelyn [Presence-PC]	20 Aug 2001 11:42
Sinisa Milivojevic	20 Aug 2001 11:50
Fournier Jocelyn [Presence-PC]	20 Aug 2001 11:58
Sasha Pachev	20 Aug 2001 12:10
Fournier Jocelyn [Presence-PC]	20 Aug 2001 13:39
Sasha Pachev	20 Aug 2001 13:47
Fournier Jocelyn [Presence-PC]	20 Aug 2001 13:57
Fournier Jocelyn [Presence-PC]	20 Aug 2001 17:35
Sasha Pachev	20 Aug 2001 17:48
Fournier Jocelyn [Presence-PC]	20 Aug 2001 18:07
Fournier Jocelyn [Presence-PC]	20 Aug 2001 18:11
Michael Widenius	21 Aug 2001 02:21
Michael Widenius	21 Aug 2001 03:09
Michael Widenius	21 Aug 2001 04:13

Subject:	Re: error 127 from table handler with latest mysql 4.0.0 sources.
From:	Sasha Pachev (sas...@mysql.com)
Date:	08/20/2001 01:47:01 PM
List:	com.mysql.lists.bugs

On Monday 20 August 2001 14:39, Fournier Jocelyn [Presence-PC] wrote:

Hi,

I need some help with the mysqltest syntax :

Congratulations. You are the first person outside the company known to us who actually tried to write a test case with it.

I try to make this test case :

connect (con1, localhost, root,,); connect (con2, localhost, root,,);

connection con1; let $1=10; while ($1) { send select * from presence.inscrit LIMIT 0,100; dec $1; } --sleep 10

connection con2; #--error 1030 send INSERT into presence.inscrit2 SELECT * FROM presence.inscrit; --sleep 5 connection con1; @./res1 reap;

connection con2; @./res2 reap;

res1 is created successfully, but res2 is not created. Why ?

Because INSERT produces no result set. So the above is ok. You can also remove @ syntax and use --result-file=/path/to/result-file on the command line.

Thank you :)

(BTW, I've got some new error in my .err file : 010820 20:07:35 read_const: Got error 127 when reading table ./presence/tabban 010820 20:14:57 read_last_with_key: Got error 127 when reading table 010820 20:21:14 read_prev_with_key: Got error 127 when reading table: ./presence/news 010820 22:30:37 read_last_with_key: Got error 134 when reading table

There is definitely a big bug as a never see those kind of errors, and there appear on my two servers since I installed the latest mysql 4.0.0 source)

When you have a full test that starts with a clean table and corrupts it, send it to us and we will take a look at it...