- 13 Sep, 2006 2 commits
- 12 Sep, 2006 1 commit
-
-
unknown authored
Bug #21378 Alter table from X storage engine to NDB could cause data loss: Added warning if local table shadows ndb table
-
- 15 Aug, 2006 2 commits
-
-
unknown authored
into mysql.com:/windows/Linux_space/MySQL/mysql-4.1
-
unknown authored
bug #18184 SELECT ... FOR UPDATE does not work..: New test case ha_ndbcluster.h, ha_ndbcluster.cc, NdbConnection.hpp: Fix for bug #21059 Server crashes on join query with large dataset with NDB tables: Releasing operation for each intermediate batch, before next call to trans->execute(NoCommit); mysql-test/r/ndb_lock.result: bug #18184 SELECT ... FOR UPDATE does not work..: New test case mysql-test/t/ndb_lock.test: bug #18184 SELECT ... FOR UPDATE does not work..: New test case ndb/include/ndbapi/NdbConnection.hpp: Fix for bug #21059 Server crashes on join query with large dataset with NDB tables: Releasing operation for each intermediate batch, before next call to trans->execute(NoCommit); sql/ha_ndbcluster.cc: Fix for bug #21059 Server crashes on join query with large dataset with NDB tables: Releasing operation for each intermediate batch, before next call to trans->execute(NoCommit); sql/ha_ndbcluster.h: Fix for bug #21059 Server crashes on join query with large dataset with NDB tables: Releasing operation for each intermediate batch, before next call to trans->execute(NoCommit);
-
- 14 Aug, 2006 6 commits
-
-
unknown authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-4.1-bug9678
-
unknown authored
Socket timeouts in client library were used only on Windows. The solution is to use socket timeouts in client library on all systems were they are supported. No test case is provided because it is impossible to simulate network failure in current test suit. sql/net_serv.cc: Retry indefinitely only if got EINTR. vio/viosocket.c: Set socket timeouts on POSIX systems as well as on Windows.
-
unknown authored
into april.(none):/home/svoj/devel/mysql/BUG18874/mysql-4.1
-
unknown authored
Fixed by moving update_key_parts() down to be after write_index(). myisam/sort.c: write_index() collects index statistic which is further used in update_key_parts(). Thus update_key_parts() must be called after write_index(). mysql-test/r/repair.result: Test case for bug#18874. mysql-test/t/repair.test: Test case for bug#18874.
-
unknown authored
mysql-test/r/heap_btree.result: Make the heap_btree test repeatable. - 'order by' added where we don't use the 'a' index. mysql-test/t/heap_btree.test: Make the heap_btree test repeatable. - 'order by' added where we don't use the 'a' index.
-
unknown authored
sql/set_var.cc: Restore alphabetical order of the system variables. - moved the have_merge_engine variable.
-
- 11 Aug, 2006 3 commits
-
-
unknown authored
into mysql.com:/usr/home/bar/mysql-4.1.b15276
-
unknown authored
didn't work as expected: collation_server was set not to xxx, but to the default collation of character set "yyy". With different argument order it worked as expected: mysqld --character-set-server=yyy --collation-server=yyy Fix: initializate default_collation_name to 0 when processing --character-set-server only if --collation-server has not been specified in command line. mysql-test/r/ctype_ucs2_def.result: Adding test cast mysql-test/t/ctype_ucs2_def-master.opt: Adding test case mysql-test/t/ctype_ucs2_def.test: Adding test case sql/mysqld.cc: Don't clear default_collation_name when processing --character-set-server if collation has already been specified using --collation-server
-
unknown authored
--with-collation worked only on the server side. Client side ignored this argument, so collation_connection was not properly set (remained latin1_swedish_ci). sql-common/client.c: - Take into account MYSQL_DEFAULT_COLLATION_NAME if character set is not set using mysql_option(), to honor --with-collation argument to configure. - Use default collation for the character set when it's not set using mysql_option().
-
- 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 1 commit
-
-
unknown authored
into mysql.com:/Users/kent/mysql/bk/mysql-4.1 configure.in: Auto merged
-