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

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

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

  More explicit naming of variables

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

  remove dict forwarding
  add api retries on NotMaster
  

into here.mwagner.org:/Users/mwagner/work/bk/mysql-4.1

  Add new manual.texi include files

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

into mysql.com:/home/bk/b8412-mysql-4.0

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

start_waiting_global_read_lock() should wake up all those who are waiting
for protect_against_global_read_lock to go down to 0: those registered in waiting_for_read_lock
AND those registered in global_read_lock_blocks_commit.

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

  Activate Unicode collations in Windows version.

   make sure transporter connections are close early in shutdown

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

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

  Fix bug #8677: if one used LOCK TABLES, created an InnoDB temp table, and did a multi-table update where a MyISAM table was the update table and the temp table was a read table, then InnoDB aserted in row0sel.c because n_mysql_tables_in_use was 0. Also, we remove the assertion altogether and just print an error to the .err log if this important consistency check fails. Then it is up to the user to read the .err log and notice the problem if there still are errors in MySQL's table locking.

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

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

What we need to be able to set in myisamchk is
actually a collation, not a character set. This
fix just changes to display the proper error message. 

into 51.0.168.192.in-addr.arpa:/Users/bell/mysql/bk/work-4.1