- 14 Sep, 2007 5 commits
-
-
istruewing@stella.local authored
into stella.local:/home/mydev/mysql-5.1-axmrg
-
istruewing@stella.local authored
into stella.local:/home/mydev/mysql-5.1-axmrg
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.1-opt
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.1-opt
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.0-opt
-
- 13 Sep, 2007 9 commits
-
-
joerg@trift2. authored
into trift2.:/MySQL/M51/tmp-5.1
-
joerg@trift2. authored
into trift2.:/MySQL/M51/tmp-5.1
-
joerg@trift2. authored
into trift2.:/MySQL/M50/tmp-5.0
-
svoj@june.mysql.com authored
into mysql.com:/home/svoj/devel/mysql/BUG30590/mysql-5.1-engines
-
svoj@june.mysql.com authored
into mysql.com:/home/svoj/devel/mysql/BUG30590/mysql-5.0-engines
-
svoj@mysql.com/june.mysql.com authored
DELETE query against memory table with btree index may remove not all matching rows. This happens only when DELETE uses index read method to find matching rows. E.g. for queries like DELETE FROM t1 WHERE a=1. Fixed by reverting fix for BUG9719 and applying proper solution.
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.1-opt
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.0-opt
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.1-opt
-
- 12 Sep, 2007 5 commits
-
-
gshchepa/uchum@gleb.loc authored
Post-merge fix.
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.1-opt
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.0-opt
-
sergefp@mysql.com authored
-
gshchepa@bk-internal.mysql.com authored
into bk-internal.mysql.com:/data0/bk/mysql-5.1-opt
-
- 11 Sep, 2007 2 commits
-
-
sergefp@mysql.com authored
-
holyfoot/hf@mysql.com/hfmain.(none) authored
-
- 10 Sep, 2007 4 commits
-
-
sergefp@mysql.com authored
-
sergefp@pylon.mylan authored
into mysql.com:/home/psergey/mysql-5.0-bug30385
-
sergefp@mysql.com authored
in get_index_for_order(), don't walk over the end of the index key parts when matching index description and needed ordering.
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/28430/my51-28430
-
- 07 Sep, 2007 1 commit
-
-
holyfoot/hf@mysql.com/hfmain.(none) authored
In the ha_partition::position() we don't calculate the number of the partition of the record, but use m_last_part value instead, relying on that it's previously set by some other call like ::write_row(). Delete_rows_log_event::do_exec_row() calls find_and_fetch_row(), where we used position() + rnd_pos() call for the InnoDB-based PARTITION-ed table as there HA_PRIMARY_KEY_REQUIRED_FOR_POSITION enabled. fixed by introducing new handler::rnd_pos_by_record() method to be used for random record-based positioning
-
- 06 Sep, 2007 10 commits
-
-
malff@omega.weblab authored
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.1-opt
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.1-opt
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.0-opt
-
gshchepa/uchum@gleb.loc authored
Post-merge fix.
-
davi@moksha.local authored
into moksha.local:/Users/davi/mysql/push/mysql-5.1-runtime
-
davi@moksha.local authored
the first query is not running while we are doing wait queries on a second connection.
-
gshchepa/uchum@gleb.loc authored
Post-merge fix.
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.1-opt
-
dlenev@mockturtle.local authored
-
- 05 Sep, 2007 4 commits
-
-
malff@omega.weblab authored
into omega.weblab:/home/malff/TREE/mysql-5.1-rt-merge
-
malff@omega.weblab authored
into omega.weblab:/home/malff/TREE/mysql-5.1-cleanup
-
malff@omega.weblab authored
Fixed test failure under heavy load, in case truncate table is slow.
-
davi@moksha.local authored
the first query is not running while we are doing wait queries on a second connection.
-