An error occurred fetching the project authors.
  1. 23 Feb, 2007 1 commit
    • gkodinov/kgeorge@macbook.gmz's avatar
      Bug #26186: · f88aec9e
      gkodinov/kgeorge@macbook.gmz authored
      When handling DELETE ... FROM if there is no
      condition it is internally transformed to 
      TRUNCATE for more efficient execution by the
      storage handler.
      The check for validity of the optional ORDER BY 
      clause is done after the check for the above 
      optimization and will not be performed if the
      optimization can be applied.
      Moved the validity check for ORDER BY before 
      the optimization so it performed regardless of
      the optimization.
      f88aec9e
  2. 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
  3. 27 Oct, 2006 1 commit
  4. 04 Sep, 2006 1 commit
    • gkodinov/kgeorge@macbook.gmz's avatar
      Bug #21392: multi-table delete with alias table name fails with · 3758b975
      gkodinov/kgeorge@macbook.gmz authored
                  1003: Incorrect table name
      in multi-table DELETE the set of tables to delete from actually 
      references then tables in the other list, e.g:
      DELETE alias_of_t1 FROM t1 alias_of_t1 WHERE ....
      is a valid statement.
      So we must turn off table name syntactical validity check for alias_of_t1 
      because it's not a table name (even if it looks like one).
      In order to do that we add a special flag (TL_OPTION_ALIAS) to 
      disable the name checking for the aliases in multi-table DELETE.
      3758b975
  5. 23 Jul, 2006 1 commit
  6. 28 Jul, 2005 1 commit
  7. 30 May, 2005 1 commit
  8. 16 Feb, 2005 1 commit
    • igor@rurik.mysql.com's avatar
      delete.result, delete.test: · d4779d35
      igor@rurik.mysql.com authored
        Added a test case for bug #8392.
      sql_delete.cc:
        Fixed bug #8392.
        The bug caused a crash for a delete statement with ORDER BY
        that explicitly referred to the modified table.
      d4779d35
  9. 22 Nov, 2004 1 commit
  10. 01 Oct, 2004 1 commit
    • ram@gw.mysql.r18.ru's avatar
      delete.result, delete.test: · 4ec50dc4
      ram@gw.mysql.r18.ru authored
        A fix (bug #5733: Table handler error with self-join multi-table DELETE).
      records.cc:
        A fix (bug #5733: Table handler error with self-join multi-table DELETE).
      4ec50dc4
  11. 21 Jun, 2004 1 commit
  12. 16 Feb, 2004 1 commit
    • monty@mysql.com's avatar
      After merge fixes · f43093ec
      monty@mysql.com authored
      Added more DBUG statements
      Ensure that we are comparing end space with BINARY strings
      Use 'any_db' instead of '' to mean any database. (For HANDLER command)
      Only strip ' ' when comparing CHAR, not other space-like characters (like \t)
      f43093ec
  13. 10 Dec, 2003 1 commit
  14. 17 Nov, 2003 1 commit
  15. 03 May, 2003 1 commit
  16. 17 Mar, 2003 1 commit
  17. 04 Mar, 2003 1 commit
  18. 05 Jan, 2003 1 commit
  19. 15 Dec, 2002 1 commit
  20. 23 Nov, 2002 1 commit
  21. 21 Nov, 2002 1 commit
  22. 31 Aug, 2002 1 commit
  23. 30 Aug, 2002 1 commit
  24. 28 Dec, 2000 1 commit
  25. 21 Dec, 2000 1 commit