RUN BEFORE

Problem:
Table's cond_set bitmap gets set when the first query in the bugpage
is run. The same value for cond_set is used for the second query too
as the bits are not reset. As a result, optimizer tries to calculate
condition filtering effect for the second query when there are no
predicates on the fields of the table, resulting in the extra trace.
Query execution does not get affected because the other checks do not
pass.

Solution:
Reset the bitmap "cond_set" in clear_column_bitmaps() similar to other
bitmaps.TABLE::init() calls clear_column_bitmaps() there by resetting
the bitmap for the next query.

Reviewed by: Dag Wanvik <dag.wanvik@oracle.com>