• evgen@moonbone.local's avatar
    Fix bug#11482 4.1.12 produces different resultset for a complex query · 0298bc34
    evgen@moonbone.local authored
      than in previous 4.1.x
    
    Wrongly applied optimization were adding NOT NULL constraint which results in
    rejecting valid rows and reduced result set.
    
    The problem was that add_notnull_conds() while checking subquery were adding
    NOT NULL constraint to left joined table, to which, normally, optimization 
    don't have to be applied.
    0298bc34
select.result 64.4 KB