- 29 Nov, 2007 3 commits
-
-
ramil/ram@ramil.myoffice.izhnet.ru authored
into mysql.com:/home/ram/work/b32726/b32726.5.0
-
into mysql.com:/home/ram/work/b32559/b32559.5.0
-
ramil/ram@ramil.myoffice.izhnet.ru authored
into mysql.com:/home/ram/work/b32676/b32676.5.0
-
- 28 Nov, 2007 2 commits
-
-
istruewing@stella.local authored
Disabled test case.
-
- fix for #31070 (missed during merging) applied for cp932 charset. - tests/results adjusted.
-
- 27 Nov, 2007 8 commits
-
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-5.0-axmrg
-
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-5.0-axmrg
-
istruewing@stella.local authored
Disabled the test case.
-
ramil/ram@ramil.myoffice.izhnet.ru authored
into mysql.com:/home/ram/work/b30495/b30495.5.0
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-5.0-axmrg
-
into mysql.com:/home/ram/work/b30495/b30495.5.0
-
Problem: passing a non-constant name to the NAME_CONST function results in a crash. Fix: check the NAME_CONST name argument; return fake item type if we got non-constant argument(s).
-
- 26 Nov, 2007 4 commits
-
-
istruewing@stella.local authored
Bug#20627 - INSERT DELAYED does not honour auto_increment_* variables Fixed wrong variable assignment.
-
istruewing@stella.local authored
Disabled test case
-
istruewing@stella.local authored
Another try to fix a compiler warning on win64.
-
Problem: using wrong local lock type value in the mysql_insert() results in a crash. Fix: use a proper value.
-
- 25 Nov, 2007 1 commit
-
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-5.0-axmrg
-
- 23 Nov, 2007 8 commits
-
-
into mysql.com:/home/ram/work/b32560/b32560.5.0
-
Problem: INTERVAL function implementation doesn't handle NULL range values. Fix: skip NULL ranges looking for a proper one.
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-5.0-axmrg
-
istruewing@stella.local authored
Disabled test case
-
istruewing@stella.local authored
Disabled test case
-
istruewing@stella.local authored
Fixed a compiler warning on win64. Backport from 5.1.
-
istruewing@stella.local authored
Disabled test case
-
into mysql.com:/home/ram/work/b32558/b32558.5.0
-
- 21 Nov, 2007 12 commits
-
-
mkindahl@dl145h.mysql.com authored
into dl145h.mysql.com:/data0/mkindahl/mysql-5.0-rpl-merge
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-5.0-axmrg
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-5.0-axmrg
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-4.1-axmrg
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.0-build
-
df@pippilotta.erinye.com authored
-
mleich@five.local.lan authored
into five.local.lan:/work/trees/mysql-5.0-build-src-clean
-
df@pippilotta.erinye.com authored
-
Problem: setting Item_func_rollup_const::null_value property to argument's null_value before (without) the argument evaluation may result in a crash due to wrong null_value. Fix: use is_null() to set Item_func_rollup_const::null_value instead as it evaluates the argument if necessary and returns a proper value.
-
mleich@five.local.lan authored
Bug#31567 "datadict" tests (all engines) fail: Reference protocol is non-standard build Bug#30418 "datadict" tests (all engines) fail: Dependency on the host name for ordering Modifications: 1. The standard builds (build team) do not contain the collation 'utf8_general_cs'. The common developer builds (compuile-....-max) contain this collation. Solution fitting to both build variants: Exclude the collation 'utf8_general_cs' from result sets. 2. Use mysqltest builtin sorting of result set for the statement where the hostname affects the row order.
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-5.0-axmrg
-
Problem: we have CHECK TABLE options allowed (by accident?) for ANALYZE/OPTIMIZE TABLE. Fix: disable them. Note: it might require additional fixes in 5.1/6.0
-
- 20 Nov, 2007 2 commits
-
-
tsmith@ramayana.hindu.god authored
Fixes the following bugs: - Bug #29560: InnoDB >= 5.0.30 hangs on adaptive hash rw-lock 'waiting for an X-lock' Fixed a race condition in the rw_lock where an os_event_reset() can overwrite an earlier os_event_set() triggering an indefinite wait. NOTE: This fix for windows is different from that for other platforms. NOTE2: This bug is introduced in the scalability fix to the sync0arr which was applied to 5.0 only. Therefore, it need not be applied to the 5.1 tree. If we decide to port the scalability fix to 5.1 then this fix should be ported as well. - Bug #32125: Database crash due to ha_innodb.cc:3896: ulint convert_search_mode_to_innobase When unknown find_flag is encountered in convert_search_mode_to_innobase() do not call assert(0); instead queue a MySQL error using my_error() and return the error code PAGE_CUR_UNSUPP. Change the functions that call convert_search_mode_to_innobase() to handle that error code by "canceling" execution and returning appropriate error code further upstream.
-
kent@kent-amd64.(none) authored
into mysql.com:/home/kent/bk/tmpmerge/mysql-5.0-build
-