- 28 Sep, 2006 1 commit
-
-
unknown authored
into dev3-76.dev.cn.tlan:/home/dli/mysql/mysql-4.1/mysql-4.1-bug-19651
-
- 26 Sep, 2006 1 commit
-
-
unknown authored
ndb/tools/restore/consumer.hpp: added a function to judge whether there is temporary error. ndb/tools/restore/consumer_restore.cpp: record when temporary error occured in restore. ndb/tools/restore/consumer_restore.hpp: added a member to record temporary error in restore. ndb/tools/restore/restore_main.cpp: report temporary error in restore.
-
- 19 Sep, 2006 1 commit
-
-
unknown authored
and other commands related to ndb. For all of these, the help screen contains "Ndb.cfg" string. Now i change the "Ndb.cfg" to "my.cnf" because "Ndb.cfg" is obsolete. ndb/include/util/ndb_opts.h: Change help info from Ndb.cfg to my.cnf in the header file. ndb/test/ndbapi/flexScan.cpp: Change help info from Ndb.cfg to my.cnf. ndb/tools/ndb_config.cpp: Change help info from Ndb.cfg to my.cnf
-
- 15 Sep, 2006 1 commit
-
-
unknown authored
almost useless for any kind of shell script automation. Now add the return value that indicates the execution whether or not success for many methods. ndb/src/mgmclient/CommandInterpreter.cpp: Many methods add the return value that indicates whether the execution of operatioin succeeds. This can make ndb_mgm management client set the exit status on errors.
-
- 01 Sep, 2006 1 commit
-
-
unknown authored
Fixed the cluster logfile rotation code, let the cluster logfile be renamed correctly when the main logfile exceeds the configured maximum size. ndb/include/util/File.hpp: Fix for BUG#21345, Error in cluster logfile rotation. ndb/src/common/logger/FileLogHandler.cpp: Fix for BUG#21345, Error in cluster logfile rotation. ndb/src/common/util/File.cpp: Fix for BUG#21345, Error in cluster logfile rotation.
-
- 10 Aug, 2006 1 commit
-
-
unknown authored
myisam/mi_uniue.c:mi_check_unique() should skip trailing spaces comparing TEXT and VARTTEXT key segments. myisam/mi_unique.c: Fix for bug #20709: Collation not used in group by on 4.1. myisam/mi_uniue.c:mi_check_unique() should skip trailing spaces comparing TEXT and VARTTEXT key segments. Example: assume, we have a 'char(200) collate utf8_unicode_ci' field, there are two records with _utf8"0x65" and _utf8"0xC3A9" characters; these values are equal according to the utf8_unicode_ci collation, but two 600 byte length corresponding keys: "0x65<0x20 repeats 599 times>" and "0xC3A9<0x20 repeats 598 times>" are not equal if we count trailing spaces and it may cause inconsequent behavior. So, let's pass 1 as the skip_end_space parameter value to the mi_compare_text() function for proper TEXT and VARTTEXT key segments comparison. mysql-test/r/ctype_utf8.result: Fix for bug #20709: Collation not used in group by on 4.1. - test results. mysql-test/t/ctype_utf8.test: Fix for bug #20709: Collation not used in group by on 4.1. - test case.
-
- 09 Aug, 2006 3 commits
-
-
unknown authored
BitKeeper/deleted/.del-bug20328.test: Delete: mysql-test/t/bug20328.test BitKeeper/deleted/.del-bug20328.result: Delete: mysql-test/r/bug20328.result
-
unknown authored
into may.pils.ru:/home/svoj/devel/mysql/BUG20060/mysql-4.1
-
unknown authored
Problem described in this bug report affects MyISAM tables only. Running mysqld --flush instructs mysqld to sync all changes to disk after each SQL statement. It worked well for INSERT and DELETE statements, but it did sync for UPDATE only in case if there was index change (change of colum that has an index). If no updated column has an index, data wasn't synced to disk. This fix makes UPDATE statement to sync data to disk even if there is no index change (that is only data change) and mysqld is run with --flush option. myisam/mi_update.c: Every myisam function that updates myisam table must end with call to _mi_writeinfo(). If operation (second param of _mi_writeinfo()) is not 0 it sets share->changed to 1, that is flags that data has changed. If operation is 0, this function equals to no-op in this case. mi_update() must always pass !0 value as operation, since even if there is no index change there could be data change.
-
- 07 Aug, 2006 1 commit
-
-
unknown authored
into mysql.com:/usr/home/bar/mysql-4.1.b19741
-
- 03 Aug, 2006 5 commits
-
-
unknown authored
into may.pils.ru:/home/svoj/devel/mysql/BUG7391/mysql-4.1
-
unknown authored
- Backport patch from 5.0 sql/mysqld.cc: Add else case to set "lower_case_file_system" also when lower_case_table_names are 1
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1 mysql-test/t/mysqlbinlog.test: Auto merged
-
unknown authored
into may.pils.ru:/home/svoj/devel/mysql/BUG7391/mysql-4.1
-
unknown authored
privileges This problem is 4.1 specific. It doesn't affect 4.0 and was fixed in 5.x before. Having any mysql user who is allowed to issue multi table update statement and any column/table grants, allows this user to update any table on a server (mysql grant tables are not exception). check_grant() accepts number of tables (in table list) to be checked in 5-th param. While checking grants for multi table update, number of tables must be 1. It must never be 0 (actually we have DBUG_ASSERT(number > 0) in 5.x in grant_check() function). mysql-test/r/grant.result: Addition to test case for bug#7391: - Added grant statement to trigger this problem in 4.1. - Fixed error messages. mysql-test/t/grant.test: Addition to test case for bug#7391: - Added grant statement to trigger this problem in 4.1. - Fixed error messages. sql/sql_update.cc: check_grant() accepts number of tables (in table list) to be checked in 5-th param. For this particular check number of tables must be 1. It must never be 0 (actually we have DBUG_ASSERT(number > 0) in 5.x in grant_check() function).
-
- 02 Aug, 2006 7 commits
-
-
unknown authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/m41-maint--07OBQ sql/set_var.cc: Auto merged
-
unknown authored
set. (Ramil's patch, recreated.) heap/hp_delete.c: Reset info->lastkey_len for further heap_rnext/heap_rprev calls. mysql-test/r/heap_btree.result: Test for bug #9719: DELETE with WHERE on HEAP table just deletes first row of matched set. mysql-test/t/heap_btree.test: Test for bug #9719: DELETE with WHERE on HEAP table just deletes first row of matched set.
-
unknown authored
into rolltop.ignatz42.dyndns.org:/mnt/storeage/mysql-4.1-maint_bug20721
-
unknown authored
into moonbone.local:/work/tmp_merge-4.1-opt-mysql
-
unknown authored
into moonbone.local:/work/tmp_merge-4.1-opt-mysql
-
unknown authored
into moonbone.local:/work/tmp_merge-4.1-opt-mysql sql/item_strfunc.cc: Auto merged sql/mysql_priv.h: Auto merged sql/sql_parse.cc: Auto merged sql/sql_select.cc: Auto merged
-
unknown authored
into mysql.com:/home/hf/work/mysql-4.1.20317
-
- 01 Aug, 2006 2 commits
- 31 Jul, 2006 5 commits
-
-
unknown authored
into anubis.greendragongames.com:/home/greenman/workspace-mysql/mysql/pending/bug-4.1-19364 client/mysql.cc: Auto merged
-
unknown authored
into mysql.com:/users/lthalmann/bk/MERGE/mysql-4.1-merge
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1
-
- 30 Jul, 2006 1 commit
-
-
unknown authored
- Init start_lineno to 0 client/mysqltest.c: Init start_lineno to 0 and set it back to zero before comparing result file.
-
- 29 Jul, 2006 2 commits
- 28 Jul, 2006 4 commits
-
-
unknown authored
into mysql.com:/Users/kent/mysql/bk/mysql-4.1 configure.in: Auto merged scripts/make_binary_distribution.sh: Auto merged support-files/mysql.spec.sh: SCCS merged
-
unknown authored
Man page for mysqld command move to section 8 (bug#21220) configure.in: Man page for mysqld command move to section 8 (bug#21220) man/Makefile.am: Man page for mysqld command move to section 8 (bug#21220)
-
unknown authored
Man page for "mysqld" command move to section 8 (bug#21220) scripts/make_binary_distribution.sh: Man page for "mysqld" command move to section 8 (bug#21220)
-
unknown authored
Man page for "mysqld" command move to section 8 (bug#21220) support-files/mysql.spec.sh: Man page for "mysqld" command move to section 8 (bug#21220)
-
- 27 Jul, 2006 1 commit
-
-
unknown authored
into rakia.(none):/home/kgeorge/mysql/autopush/B20792-4.1-opt sql/sql_select.cc: Auto merged
-
- 26 Jul, 2006 3 commits
-
-
unknown authored
into rakia.(none):/home/kgeorge/mysql/autopush/B20792-4.1-opt sql/sql_select.cc: Auto merged
-
unknown authored
When processing aggregate functions all tables values are reset to NULLs at the end of each group. When doing that if there are no rows found for a group the const tables must not be reset as they are not recalculated by do_select()/sub_select() for each group. mysql-test/r/subselect2.result: * Bug #20792: Incorrect results from aggregate subquery - test suite for the bug. This is dependent on InnoDB despite the fact that the bug and the fix are not InnoDB specific. This is because of the table flag HA_NOT_EXACT_COUNT. When this flag is off (as in MyISAM) both t2 and t3 become of join type 'system' as they are estimated to have 1 record and and this statistics can be trusted (according to the absence of HA_NOT_EXACT_COUNT). mysql-test/t/subselect2.test: * Bug #20792: Incorrect results from aggregate subquery - test suite for the bug sql/sql_select.cc: * Bug #20792: Incorrect results from aggregate subquery - when clearing results if there are not rows found for group the const tables must not be reset as they are not recalculated for each group.
-
unknown authored
into rakia.(none):/home/kgeorge/mysql/autopush/B21019-4.1-opt sql/sql_select.cc: Auto merged mysql-test/r/select.result: SCCS merged mysql-test/t/select.test: SCCS merged
-