1. 11 Jan, 2007 1 commit
    • evgen@moonbone.local's avatar
      Bug#17711: DELETE doesn't use index when ORDER BY, LIMIT and non-restricting · c17bf5cb
      evgen@moonbone.local authored
      WHERE is present.
      
      If a DELETE statement with ORDER BY and LIMIT contains a WHERE clause
      with conditions that for sure cannot be used for index access (like in
      WHERE @var:= field) the execution always follows the filesort path.    
      It happens currently even when for the above case there is an index that
      can be used to speedup sorting by the order by list.
      
      Now if a DELETE statement with ORDER BY and LIMIT contains such WHERE
      clause conditions that cannot be used to build any quick select then
      the mysql_delete() tries to use an index like there is no WHERE clause at all.
      c17bf5cb
  2. 12 Dec, 2006 1 commit
  3. 11 Dec, 2006 1 commit
  4. 06 Dec, 2006 2 commits
  5. 05 Dec, 2006 6 commits
  6. 04 Dec, 2006 4 commits
  7. 01 Dec, 2006 2 commits
  8. 30 Nov, 2006 4 commits
  9. 29 Nov, 2006 9 commits
  10. 28 Nov, 2006 10 commits