1. 20 Sep, 2005 3 commits
  2. 19 Sep, 2005 16 commits
  3. 18 Sep, 2005 5 commits
  4. 17 Sep, 2005 3 commits
  5. 16 Sep, 2005 12 commits
  6. 15 Sep, 2005 1 commit
    • evgen@moonbone.local's avatar
      Fix bug #12291 Table wasn't reinited for index scan after sequential scan · 097ca8ad
      evgen@moonbone.local authored
      Optimizer did choose "Range checked for each record" for one of the tables.
      For first few loops over that table it choose sequential access, on later
      stage it choose to use index. Because table was previously initialized for 
      sequential access, it skips intitialization for index access, and when
      server tries to retrieve data error occurs.
      
      QUICK_RANGE_SELECT::init() changes so if file already initialized for
      sequential access, it calls ha_rnd_end() and initializes file for index
      access.
      097ca8ad