1. 12 Apr, 2007 16 commits
  2. 11 Apr, 2007 20 commits
  3. 10 Apr, 2007 4 commits
    • gkodinov/kgeorge@magare.gmz's avatar
      Bug #19372: · 9514ac9f
      gkodinov/kgeorge@magare.gmz authored
      Added a test case.
      The problem was fixed by the fix for bug #17379.
      The problem was that because of some conditions 
      the optimizer always preferred range or full index
      scan access methods to lookup access methods even
      when the latter were much cheaper.
      9514ac9f
    • gkodinov/kgeorge@magare.gmz's avatar
      Merge gkodinov@bk-internal.mysql.com:/home/bk/mysql-5.0-opt · 21a13688
      gkodinov/kgeorge@magare.gmz authored
      into  magare.gmz:/home/kgeorge/mysql/autopush/B27659-5.0-opt
      21a13688
    • gkodinov/kgeorge@magare.gmz's avatar
      Bug #27659: · aefc060f
      gkodinov/kgeorge@magare.gmz authored
      The optimizer transforms DISTINCT into a GROUP BY
      when possible.
      It does that by constructing the same structure
      (a list of ORDER instances) the parser makes when
      parsing GROUP BY.
      While doing that it also eliminates duplicates.
      But if a duplicate is found it doesn't advance the
      pointer to ref_pointer array, so the next 
      (and subsequent) ORDER structures point to the wrong
      element in the SELECT list.
      Fixed by advancing the pointer in ref_pointer_array
      even in the case of a duplicate.
      aefc060f
    • gluh@mysql.com/eagle.(none)'s avatar
      Merge sgluhov@bk-internal.mysql.com:/home/bk/mysql-5.0-opt · 6b2cb10a
      gluh@mysql.com/eagle.(none) authored
      into  mysql.com:/home/gluh/MySQL/Bugs/5.0.27069
      6b2cb10a