into  mats-laptop.(none):/home/bk/b29020-mysql-5.1-rpl

into  moonbone.local:/work/27219-bug-5.1

into  mysql.com:/home/ram/work/mysql-5.1-bugteam

after few delete statements

Problem: changing a file size might require that it must be 
unmapped beforehand.
  
Fix: unmap the file before changing its size.

into  moonbone.local:/work/27219-bug-5.1

into  witty.:/Users/mattiasj/clones/bug21413-51-bugteam

into  mats-laptop.(none):/home/bk/b29020-mysql-5.1-rpl

into  witty.:/Users/mattiasj/clones/bug21413-51-engines

into  witty.:/Users/mattiasj/clones/bug21413-50-engines

            in REPLACE DELAYED
    
post push patch, removing the optimization for
copying delayed_insert variables.

The bug allow multiple executing transactions working with non-transactional
to interfere with each others by interleaving the events of different trans-
actions.

Bug is fixed by writing non-transactional events to the transaction cache and
flushing the cache to the binary log at statement commit. To mimic the behavior
of normal statement-based replication, we flush the transaction cache in row-
based mode when there is no committed statements in the transaction cache,
which means we are committing the first one. This means that it will be written
to the binary log as a "mini-transaction" with just the rows for the statement.

Note that the changes here does not take effect when building the server with
HAVE_TRANSACTIONS set to false, but it is not clear if this was possible before
this patch either.

For row-based logging, we also have that when AUTOCOMMIT=1, the code now always
generates a BEGIN/COMMIT pair for single statements, or BEGIN/ROLLBACK pair in the
case of non-transactional changes in a statement that was rolled back. Note that
for the case where changes to a non-transactional table causes a rollback due
to error, the statement will now be logged with a BEGIN/ROLLBACK pair, even
though some changes has been committed to the non-transactional table.

into  moonbone.local:/work/27219-5.0-opt-mysql

into  magare.gmz:/home/kgeorge/mysql/work/merge-5.1-bugteam

into  magare.gmz:/home/kgeorge/mysql/work/merge-5.1-bugteam

into  magare.gmz:/home/kgeorge/mysql/work/merge-5.0-bugteam

into  magare.gmz:/home/kgeorge/mysql/work/merge-5.1-bugteam

into  magare.gmz:/home/kgeorge/mysql/work/merge-5.1-bugteam

into  magare.gmz:/home/kgeorge/mysql/work/merge-5.1-bugteam

into  magare.gmz:/home/kgeorge/mysql/work/merge-5.0-bugteam

into  magare.gmz:/home/kgeorge/mysql/work/merge-5.1-bugteam

into  magare.gmz:/home/kgeorge/mysql/autopush/B35206-5.1-bugteam

into  mysql.com:/misc/mysql/mysql-5.1-opt

into  mysql.com:/misc/mysql/mysql-5.0-opt

into  mysql.com:/misc/mysql/mysql-5.1-opt

The code for executing indexed ORDER BY was not setting all the 
internal fields correctly when selecting to execute ORDER BY over
and index.
Fixed by change the access method to one that will use the 
quick indexed access if one is selected while selecting indexed
ORDER BY.

Mixing aggregate functions and non-grouping columns is not allowed in the
ONLY_FULL_GROUP_BY mode. However in some cases the error wasn't thrown because
of insufficient check.

In order to check more thoroughly the new algorithm employs a list of outer
fields used in a sum function and a SELECT_LEX::full_group_by_flag.
Each non-outer field checked to find out whether it's aggregated or not and
the current select is marked accordingly.
All outer fields that are used under an aggregate function are added to the
Item_sum::outer_fields list and later checked by the Item_sum::check_sum_func
function.

reverting test that has been obsoleted by changes to the code

into  host.loc:/home/uchum/work/5.1-opt

into  host.loc:/home/uchum/work/5.0-opt

into  witty.:/Users/mattiasj/clones/bug21413-51-engines

into  witty.:/Users/mattiasj/clones/bug21413-50-engines

Fixed interference between tests: Users were added but not properly removed.
This caused later tests to fail.

into  trift2.:/MySQL/M51/push-5.1

into  trift2.:/MySQL/M51/push-5.1

into  trift2.:/MySQL/M50/push-5.0

into  trift2.:/MySQL/M51/push-5.1

into  mysql.com:/Users/davi/mysql/mysql-5.0-bugteam

into  host.loc:/home/uchum/work/5.1-opt

into  pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.1-build