after the previous run had some failures, provided it did not totally crash.

Secondary weight out of bounds was picked up in mistake when
the string is empty, instead of returning 0.

into mysql.com:/home/jonas/src/mysql-4.1

into mysql.com:/home/psergey/mysql-4.1-bugs

into mysql.com:/usr/home/ram/work/4.1

into mysql.com:/home/mysql_src/mysql-4.1-clean

in slave SQL thread: if a transaction fails because of InnoDB deadlock or innodb_lock_wait_timeout exceeded,
optionally retry the transaction a certain number of times (new variable --slave_transaction_retries).

Added a check, if the table, which we are going to create, is open.
This can happen if a MERGE mapped table is TRUNCATEd.

CREATE INDEX and DROP INDEX every 10,000 rows,
similar to ALTER TABLE.

into mysql.com:/home/jonas/src/mysql-4.1

into mysql.com:/home/jonas/src/mysql-4.1

into mysql.com:/home/jonas/src/mysql-4.1

  set exec_flag in execTC_COMMITREQ so that api will get rollbackrep

into hundin.mysql.fi:/home/marko/mysql-4.1

into mysql.com:/usr/home/ram/work/4.1.b6089

into mysql.com:/usr/home/ram/work/4.1.b6089

into mysql.com:/usr/home/ram/work/4.1.b5615

depending on ref->unsigned_flag. Item_int_with_ref can refer to both signed and 
unsigned integers.

the error to be sent to the client.

into mysql.com:/home/psergey/mysql-4.0-look

into mysql.com:/home/my/mysql-4.1

(No really critical errors found, but a few possible wrong results)

Fix for BUG#8560: Set max_sort_char for any 8-bit charset with binary collation. max_sort_char is needed by
my_like_range_simple to produce upper bound constants for LIKE "str_%" and similar expressions.

  Check if node == NULL, which means we are outside tablespace bounds, and print a big fatal error message

into hundin.mysql.fi:/home/heikki/mysql-4.1

into mysql.com:/usr/home/bar/mysql-4.1-again

  Bug#7997 Add implicit --skip-set-charset when mysqldump from 4.0 server w/ 4.1 client

into mysql.com:/usr/home/ram/work/4.1.b4802