An error occurred fetching the project authors.
- 23 Feb, 2007 1 commit
-
-
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.
-
- 11 Jan, 2007 1 commit
-
-
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.
-
- 27 Oct, 2006 1 commit
-
-
Backport of the fix for bug #8143: A date with value 0 is treated as a NULL value
-
- 04 Sep, 2006 1 commit
-
-
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.
-
- 23 Jul, 2006 1 commit
-
-
- 28 Jul, 2005 1 commit
-
-
monty@mysql.com authored
-
- 30 May, 2005 1 commit
-
-
monty@mysql.com authored
-
- 16 Feb, 2005 1 commit
-
-
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.
-
- 22 Nov, 2004 1 commit
-
-
Added check for duplicate column in key Added tests and fixed tests which exploit bug
-
- 01 Oct, 2004 1 commit
-
-
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).
-
- 21 Jun, 2004 1 commit
-
-
ram@gw.mysql.r18.ru authored
-
- 16 Feb, 2004 1 commit
-
-
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)
-
- 10 Dec, 2003 1 commit
-
-
Deprecate the use of TYPE=... Preferred syntax is ENGINE=
-
- 17 Nov, 2003 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 03 May, 2003 1 commit
-
-
serg@serg.mylan authored
-
- 17 Mar, 2003 1 commit
-
-
monty@narttu.mysql.fi authored
Don't create temporary objects with no table name
-
- 04 Mar, 2003 1 commit
-
-
serg@serg.mysql.com authored
-
- 05 Jan, 2003 1 commit
-
-
monty@mashka.mysql.fi authored
Cleaned up test; Removed wrong DROP TABLE commands and use standard table and database names. changed store_warning() -> push_warning_print()
-
- 15 Dec, 2002 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 23 Nov, 2002 1 commit
-
-
Sinisa@sinisa.nasamreza.org authored
-
- 21 Nov, 2002 1 commit
-
-
Sinisa@sinisa.nasamreza.org authored
delete from table where column<=>NULL on indexed columns
-
- 31 Aug, 2002 1 commit
-
-
serg@serg.mysql.com authored
-
- 30 Aug, 2002 1 commit
-
-
Sinisa@sinisa.nasamreza.org authored
-
- 28 Dec, 2000 1 commit
-
-
monty@donna.mysql.com authored
A lot of new tests to mysqltest Fixed bug with BDB tables and autocommit
-
- 21 Dec, 2000 1 commit
-
-
tim@cane.mysql.fi authored
Test delete from BDB table using hidden primary key.
-