This allows use to use INSERT IGNORE ... ON DUPLICATE ...

into gw.mysql.r18.ru:/usr/home/ram/work/4.1.b7281

into gw.mysql.r18.ru:/usr/home/ram/work/4.1.b7281

into deer.(none):/home/hf/work/mysql-4.1.clean

into deer.(none):/home/hf/work/mysql-4.1.clean

into mysql.com:/dbdata/psergey/mysql-4.1-order-bug

into mysql.com:/dbdata/psergey/mysql-4.1-bug6825

    moved NdbWaiter, m_ndb_cluster_connection, to impl class
    moved node selection things to cluster connection
    moved all private things to impl class
    added opts for shared memory and node selection
    changed opts handling somewhat; introduced enum for options and common handling of option variables
    added checks for transporter support
    automatic addition of shared mem transporters
    moved wait_until_ready code to cluster connection
    added control of usage of new node selection method

library: stmt_update_metadata (used when we update max_length
in mysql_stmt_store_result) needs valid row->length.

  Fix up mysql help messages.

  Convert @samp{c} to 'c', not c.

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

into ltantony.rdg.cyberkinetica.homeunix.net:/usr/home/antony/work/bug7391.4

  I fixed the typos in the transaction-isolation comments.
  I fixed the spelling mistakes in the comment.  It had tripped up a support 
  customer as they couldn't start the server with transaction-isolation=
  read-commited

  Add in missing privilege checks. 
  Tests for the privileges.

Fix for BUG#7358: removing warning reporting of mysqldump 4.1.8 when calling SHOW CREATE DATABASE, as we deal almost gracefully with it
(back to behaviour of 4.1.7). Warning was not fatal: mysqldump continued. And the good thing is that it helped spot that starting from 4.1.7,
SHOW CREATE DATABASE failed (if --single-transaction and first db has non-empty InnoDB table and there is a second db) and thus mysqldump
produced CREATE DATABASE statements missing the CHARACTER SET clause. Removing the bug which was in the server, and the warning reporting in
mysqldump (compatibility with old servers).

into mysql.com:/home/matthias/Arbeit/mysql-4.1/src

    removed TRACE from management client

into mysql.com:/home/matthias/Arbeit/mysql-4.1/src

into three.local.lan:/home/matthias/Arbeit/mysql-4.1/src

  removed methods that are duplicated in management client

  4.1.9 compatible with 4.1.8

For numeric constants we only need to add, since the parser doesn't produce 
negative numbers. 
For strings we only add (we actually could substract 1 if given string is a constant 
and it has '-number' form but we're not doing that because 
 * we set max_length bigger then necessary in other cases as well.  
 * the current solution is simpler and safer (bigger max_length is better then cutting out)

removed theCurrentConnectCounter
optimized the_release_ind by using pos[0] to indicate that there is something there
smaller storage of theDBNodes array by using Uint8
set the_relase_ind array to Uint32 to avoid possible parallell thread usage errors

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