fix for bug#8461

  BUG 8461 - TRUNCATE returns incorrect result if 2nd argument is negative
  Reason: Both TRUNCATE/ROUND converts INTEGERS to DOUBLE and back to INTEGERS
  Changed the integer routine to work on integers only.
  This bug affects 4.1, 5.0 and 5.1
  Fixing in 4.1 will need to change the routine to handle different types individually.
  5.0 did had different routines for different types already just the INTEGER routine was bad.

into  mysql.com:/space/pekka/ndb/version/my50

into  rurik.mysql.com:/home/igor/dev/mysql-5.0-0

into  rurik.mysql.com:/home/igor/dev/mysql-5.0-0

into  rurik.mysql.com:/home/igor/dev/mysql-4.1-0

into  rurik.mysql.com:/home/igor/mysql-5.0

into  rurik.mysql.com:/home/igor/dev/mysql-5.0-0

into  mysql.com:/opt/local/work/mysql-5.0-root

  manual adding the fix for bug#15828 which did not automerge

into  mysql.com.:/data/BK/mysql-5.0_15828

into  mysql.com:/opt/local/work/mysql-5.0-root

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0

When an ambiguous field name is used in a group by clause a warning is issued
in the find_order_in_list function by a call to push_warning_printf.
An expression that was not always valid was passed to this call as the field
name parameter.

into  mysql.com:/extern/mysql/work/bug15011/mysql-5.0

Added comments.

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0

  which is no longer repeatable. (Unclear when this was fixed.)

into  mysql.com:/extern/mysql/work/cantrepeat/mysql-5.0

Fix for extra zero in exponent of double values on windows.

A query with a group by and having clauses could return a wrong
result set if the having condition contained a constant conjunct 
evaluated to FALSE.
It happened because the pushdown condition for table with
grouping columns lost its constant conjuncts.
Pushdown conditions are always built by the function make_cond_for_table
that ignores constant conjuncts. This is apparently not correct when
constant false conjuncts are present.

into  mysql.com:/home/alexi/innodb/mysql-5.0-ss162

  Applied innodb-5.0-ss149/162 snapshots.

into  devsrv-b.mysql.com:/space/magnus/my41-bug15302

                               no order by clause
which was fixed by earlier changesets.
The error message is now the more generic "Unknown table ... in field list".

into  devsrv-b.mysql.com:/space/magnus/my50-bug15302

  which was fixed by earlier changesets; LOAD INDEX is not allowed in functions.
  Also testing CACHE INDEX, while OPTIMIZE and CHECK were covered by existing tests already.

into  mysql.com:/usr/local/mysql/mysql-5.0

into  devsrv-b.mysql.com:/space/magnus/my50-bug15302

into  mysql.com:/home/dlenev/src/mysql-5.0-bg16829

into  neptunus.(none):/home/msvensson/mysql/bug15302/my50-bug15302

into  mysql.com:/extern/mysql/work/bug15737/mysql-5.0