• kaa@polly.(none)'s avatar
    Fix for bug #30666: Incorrect order when using range conditions on 2 · 4aa04022
    kaa@polly.(none) authored
    tables or more
    
    The problem was that the optimizer used the join buffer in cases when
    the result set is ordered by filesort. This resulted in the ORDER BY
    clause being ignored, and the records being returned in the order
    determined by the order of matching records in the last table in join.
    
    Fixed by relaxing the condition in make_join_readinfo() to take
    filesort-ordered result sets into account, not only index-ordered ones.
    4aa04022
select.result 116 KB