- 20 Jul, 2007 1 commit
-
-
svoj@june.mysql.com authored
into mysql.com:/home/svoj/devel/mysql/BUG28838/mysql-5.0-engines
-
- 19 Jul, 2007 1 commit
-
-
svoj@mysql.com/june.mysql.com authored
to CHECK TABLE CHECK/REPAIR TABLE reports "File not found" error when issued against temporary table. Fixed by disabling a brunch of code (in case it gets temporary table) that is responsible for updating frm version as it is not needed for temporary tables.
-
- 18 Jul, 2007 1 commit
-
-
svoj@mysql.com/june.mysql.com authored
Removed duplicate call to handler::external_lock() when ALTER TABLE that doesn't need to copy a table (quick ALTER TABLE) was executed. Also quick ALTER TABLE doesn't hold LOCK_open anymore when it enables/disables indexes.
-
- 16 Jul, 2007 2 commits
-
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0-axmrg
-
-
- 14 Jul, 2007 4 commits
-
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0-axmrg
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0-axmrg
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-4.1-axmrg
-
svoj@mysql.com/april.(none) authored
pseudo_thread_id was reset to zero via mysql_change_user() handling whereas there is no reason to do that. Moreover, having two concurrent threads that change user and create a namesake temp tables leads to recording the dup pair of queries: set @@session.pseudo_thread_id = 0; CREATE temporary table `the namesake`; which will stall the slave as the second instance can not be created. And that is the bug case. Fixed by correcting pseudo_thread_id value after mysql_change_user().
-
- 09 Jul, 2007 10 commits
-
-
tsmith@sita.local authored
into sita.local:/Users/tsmith/m/bk/maint/50
-
tsmith@sita.local authored
Backport from 5.1 a fix to make this test deterministic
-
tsmith@sita.local authored
into sita.local:/Users/tsmith/m/bk/maint/50
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.0-maint
-
tsmith@sita.local authored
into sita.local:/Users/tsmith/m/bk/maint/50
-
tsmith@sita.local authored
into sita.local:/Users/tsmith/m/bk/maint/50
-
tsmith@sita.local authored
into sita.local:/Users/tsmith/m/bk/maint/41
-
tsmith@sita.local authored
into sita.local:/Users/tsmith/m/bk/maint/50
-
ramil/ram@ramil.myoffice.izhnet.ru authored
into mysql.com:/home/ram/work/b28808/b28808.5.0
-
tsmith@sita.local authored
into sita.local:/Users/tsmith/m/bk/maint/50
-
- 08 Jul, 2007 6 commits
-
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0-axmrg
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0-axmrg
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0-axmrg
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-4.1-axmrg
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-4.1-axmrg
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.0-opt
-
- 07 Jul, 2007 9 commits
-
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/dev-opt/mysql-5.0-opt-bug29417
-
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.0-opt
-
igor@olga.mysql.com authored
An assertion abort could occur for some grouping queries that employed decimal user variables with assignments to them. The problem appeared the constructors of the class Field_new_decimal because the function my_decimal_length_to_precision did not guarantee returning decimal precision not greater than DECIMAL_MAX_PRECISION.
-
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/4.1-opt
-
igor@olga.mysql.com authored
The cast operation ignored the cases when the precision and/or the scale exceeded the limits, 65 and 30 respectively. No errors were reported in these cases. For some queries this may lead to an assertion abort. Fixed by throwing errors for such cases.
-
knielsen@ymer.(none) authored
For GCov builds, if the server crashes, the normal exit handler for writing coverage information is not executed due to the abnormal termination. Fix this by explicitly calling the __gcov_flush function in our crash handler.
-
tsmith@sita.local authored
into sita.local:/Users/tsmith/m/bk/maint/50
-
- 06 Jul, 2007 6 commits
-
-
tsmith@sita.local authored
into sita.local:/Users/tsmith/m/bk/maint/50
-
tsmith@sita.local authored
into sita.local:/Users/tsmith/m/bk/maint/41
-
tsmith@sita.local authored
into sita.local:/Users/tsmith/m/bk/maint/50
-
antony@ppcg5.local authored
into ppcg5.local:/private/Network/Servers/anubis.xiphis.org/home/antony/work/mysql-5.0-engines.merge
-
antony@ppcg5.local authored
-
antony@ppcg5.local authored
Merge ppcg5.local:/private/Network/Servers/anubis.xiphis.org/home/antony/work/mysql-4.1-engines.merge into ppcg5.local:/private/Network/Servers/anubis.xiphis.org/home/antony/work/mysql-5.0-engines.merge
-