• evgen@moonbone.local's avatar
    Fixed bug #15633: Evaluation of Item_equal for non-const table caused wrong · 605f62fc
    evgen@moonbone.local authored
    select result
    
    Item equal objects are employed only at the optimize phase. Usually they are not
    supposed to be evaluated.  Yet in some cases we call the method val_int() for
    them. Here we have to take care of restricting the predicate such an object
    represents f1=f2= ...=fn to the projection of known fields fi1=...=fik.
    
    Added a check for field's table being const in Item_equal::val_int().
    If the field's table is not const val_int() just skips that field when
    evaluating Item_equal.
    605f62fc
func_group.result 34.1 KB