- 19 Jun, 2006 14 commits
-
-
lars@mysql.com authored
into mysql.com:/users/lthalmann/bk/MERGE/mysql-5.0-merge
-
anozdrin@mysql.com authored
into mysql.com:/home/alik/MySQL/devel/5.0-tree-merged
-
anozdrin@mysql.com authored
into mysql.com:/home/alik/MySQL/devel/5.0-rt
-
svoj@may.pils.ru authored
BUG#18036 - update of table joined to self reports table as crashed Set exclude_from_table_unique_test value back to FALSE. It is needed for further check in multi_update::prepare whether to use record cache.
-
lars@mysql.com authored
into mysql.com:/users/lthalmann/bk/MERGE/mysql-5.0-merge
-
lars@mysql.com authored
-
svoj@may.pils.ru authored
into may.pils.ru:/home/svoj/devel/mysql/BUG18036/mysql-5.0
-
svoj@may.pils.ru authored
into may.pils.ru:/home/svoj/devel/mysql/BUG18036/mysql-5.0
-
anozdrin@mysql.com authored
-
anozdrin@mysql.com authored
- fix for IM stopping routine; - polishing.
-
anozdrin@mysql.com authored
can be started several times; monitor interval must be > 2sec
-
lars@mysql.com authored
into mysql.com:/users/lthalmann/bk/MERGE/mysql-5.0-merge
-
svoj@may.pils.ru authored
into may.pils.ru:/home/svoj/devel/mysql/BUG18036/mysql-4.1
-
svoj@may.pils.ru authored
Certain updates of table joined to self results in unexpected behavior. The problem was that record cache was mistakenly enabled for self-joined table updates. Normally record cache must be disabled for such updates. Fixed wrong condition in code that determines whether to use record cache for self-joined table updates. Only MyISAM tables were affected.
-
- 18 Jun, 2006 3 commits
-
-
evgen@moonbone.local authored
into moonbone.local:/work/tmp_merge-5.0-opt-mysql
-
evgen@moonbone.local authored
into moonbone.local:/work/tmp_merge-5.0-opt-mysql
-
evgen@moonbone.local authored
into moonbone.local:/work/tmp_merge-4.1-opt-mysql
-
- 17 Jun, 2006 11 commits
-
-
pekka@clam.ndb.mysql.com authored
into clam.ndb.mysql.com:/space/pekka/ndb/version/my50
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.0-new
-
kent@mysql.com authored
Avoid error message trying 'windoze-dsp' in obsolete directory compile-dist: Avoid error message for target 'distclean' and no Makefile
-
pekka@clam.ndb.mysql.com authored
into clam.ndb.mysql.com:/space/pekka/ndb/version/my50-bug19285
-
pekka@clam.ndb.mysql.com authored
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.0-new
-
kent@mysql.com authored
Make output less verbose Make temporary directory name unique Remove temporary directory on interrupt
-
kent@mysql.com authored
Don't try copy non existing extra/{sql_state,mysqld_error}.h
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.0-new
-
kent@mysql.com authored
Include "sql_yacc.yy" for completeness (bug#20387)
-
kent@mysql.com authored
-
- 16 Jun, 2006 12 commits
-
-
evgen@moonbone.local authored
into moonbone.local:/work/tmp_merge-5.0-opt-mysql
-
evgen@moonbone.local authored
-
evgen@moonbone.local authored
After merge fix
-
kent@mysql.com authored
Changes for Netware
-
evgen@moonbone.local authored
-
evgen@moonbone.local authored
into moonbone.local:/work/tmp_merge-5.0-opt-mysql
-
evgen@moonbone.local authored
-
kent@mysql.com authored
Delete: netware/mysql_install.def Makefile.am: Removed obsolete "mysql_install.def"
-
evgen@moonbone.local authored
Fix for bug#16716 for --ps-protocol mode. item_cmpfunc.cc: Fix for a memory allocation/freeing problem in agg_cmp_type() after fix for bug#16377. Few language corrections.
-
dlenev@mysql.com authored
INSERT triggers". In cases when REPLACE was internally executed via update and table had on update (on delete) triggers defined we exposed the fact that such optimization used by callng on update (not calling on delete) triggers. Such behavior contradicts our documentation which describes REPLACE as INSERT with optional DELETE. This fix just disables this optimization for tables with on delete triggers. The optimization is still applied for tables which have on update but have no on delete triggers, we just don't invoke on update triggers in this case and thus don't expose information about optimization to user. Also added test coverage for values returned by ROW_COUNT() function (and thus for values returned by mysql_affected_rows()) for various forms of INSERT.
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0
-
msvensson@neptunus.(none) authored
Set default valgrind options to "-v --show-reachable=yes" and make it possible to override that with --valgrind-options
-