- 29 Jun, 2005 8 commits
-
-
-
petr@mysql.com authored
into mysql.com:/home/cps/mysql/trees/mysql-5.0
-
petr@mysql.com authored
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-bug7-5.0
-
bell@sanja.is.com.ua authored
-
ramil@mysql.com authored
into mysql.com:/usr/home/ram/work/mysql-5.0
-
ramil@mysql.com authored
-
dlenev@brandersnatch.localdomain authored
(The bug itself was fixed earlier by the patch that fixed bug #5860 "Multi-table UPDATE does not activate update triggers" and several other bugs).
-
- 28 Jun, 2005 8 commits
-
-
petr@mysql.com authored
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/mysql-5.0
-
igor@rurik.mysql.com authored
Fixed a compilation error.
-
konstantin@mysql.com authored
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-
konstantin@mysql.com authored
CURSOR_TYPE_READ_ONLY select within select". The bug was caused by the reset of thd->mem_root to thd->main_mem_root in Item_subselect::exec, which in turn triggered too early free_root() for data which was needed on subsequent fetches from a cursor. This reset also caused a memory leak in stored procedures, as subsequent executions of instructions containing a subselect were allocating memory in thd->main_mem_root, which is not freed until the end of the entire SP, instead of the per-call mem_root, which is freed in the end of execution of the instruction.
-
igor@rurik.mysql.com authored
Added a test case for bug #10031. opt_range.cc: Fixed bug #10031: range condition was not used with views. Range analyzer did not take into account that view columns were always referred through Item_ref.
-
marko@hundin.mysql.fi authored
into hundin.mysql.fi:/home/marko/mysql-5.0-current
-
- 27 Jun, 2005 18 commits
-
-
jimw@mysql.com authored
-
heikki@hundin.mysql.fi authored
Remove compiler warnings on Windows - Bug #11580
-
marko@hundin.mysql.fi authored
-
marko@hundin.mysql.fi authored
up CREATE TABLE in innodb_file_per_table=1 mode.
-
heikki@hundin.mysql.fi authored
into hundin.mysql.fi:/home/heikki/mysql-5.0
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0
-
msvensson@neptunus.(none) authored
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0
-
msvensson@neptunus.(none) authored
-
msvensson@neptunus.(none) authored
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/bug10466
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0
-
msvensson@neptunus.(none) authored
-
konstantin@mysql.com authored
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0
-
heikki@hundin.mysql.fi authored
into hundin.mysql.fi:/home/heikki/mysql-5.0
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1
-
georg@lmy002.wdf.sap.corp authored
-
- 25 Jun, 2005 1 commit
-
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.0
-
- 24 Jun, 2005 5 commits
-
-
konstantin@mysql.com authored
-
konstantin@mysql.com authored
-
konstantin@mysql.com authored
into mysql.com:/opt/local/work/mysql-5.0-join_free2push
-
konstantin@mysql.com authored
into mysql.com:/opt/local/work/mysql-5.0-join_free2push
-
konstantin@mysql.com authored
The reason it happened was that both, JOIN::cleanup() and JOIN::join_free(), went over all nested joins and called cleanup/join_free for them. For that: - split recursive and non-recursive parts of JOIN::cleanup() and JOIN::join_free() - rename JOIN::cleanup to JOIN::destroy, as it actually destroys its argument - move the recursive part of JOIN::cleanup to st_select_lex::cleanup - move the non-recursive part of JOIN::join_free to the introduced method JOIN::cleanup().
-