The problem was that when there was no MIN or MAX function, after finding the
group prefix based on the DISTINCT or GROUP BY attributes we did not search further
for a key in the group that satisfies the equi-join conditions on attributes that
follow the group attributes. Thus we ended up with the wrong rows, and subsequent
calls to select_cond->val_int() in evaluate_join_record() were filtering those
rows. Hence - the query result set was empty.

The problem occured both for GROUP BY queries without MIN/MAX and for queries
with DISTINCT (which were internally executed as GROUP BY queries).

CURSOR_TYPE_READ_ONLY". The bug was that we (me) don't perform proper
cleanups of the prepared statement when done fetching from a cursor.
Another patch.

into mysql.com:/home/svoj/devel/mysql/yassl-mysql-5.0

into mysql.com:/home/svoj/devel/mysql/yassl-mysql-5.0

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

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

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

bug#10711
bug#10058
bug#9363
bug#9025
bug#8918

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

This is to close Bug#10975, Bug#7115, Bug#10605 
This feature will be implemented in a future release.

In order to make multi-delete SP friendly we need to have all table 
locks for the elements of main statement table list properly set 
at the end of parsing.

Also performed small cleanup: We don't need relink_tables_for_multidelete()
any longer since the only case now when TABLE_LIST::correspondent_table
is non-zero are tables in auxilary table list of multi-delete and these
tables are handled specially in mysql_multi_delete_prepare().

Fix for yaSSL compilation failure on ia64 platform.

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

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

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

  Fix potential inconsistency when running ndb_restore due to faulty parsing
    of backup log wrt inserts

into mysql.com:/home/hf/work/mysql-5.0.8459

into mysql.com:/space/my/mysql-5.0

  "make install" is called (mysql_delimiter.sql was missing)

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

into mysql.com:/usr/home/ram/work/mysql-5.0

  As the bug was already fixed, just testcase added here

IPCConfig wasn't constructing the connect string properly.

into mysql.com:/usr/home/ram/work/mysql-5.0

The changes are similar to those pushed with a fix for Bug#9899,
so my guess is that ps_6dbd and ps_7ndb tests were simply not run then.

missed ityesterday :()

don't evaluate subqueries during statement prepare, even if they
are not correlated.
With post-review fixes.

(Bug which caused its failure before was fixed in the beginning of March
 by the ChangeSet that introduced improved SP-locking).

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