- 19 May, 2006 1 commit
-
-
ramil@mysql.com authored
-
- 17 May, 2006 2 commits
-
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/bug18818/my41-bug18818
-
tulin@production.mysql.com authored
into production.mysql.com:/usersnfs/tulin/mysql-4.1
-
- 16 May, 2006 9 commits
-
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1-main
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1-main
-
tomas@poseidon.ndb.mysql.com authored
ndb: ndb_waiter disconnect/reconnect on get status error
-
tulin@production.mysql.com authored
into production.mysql.com:/usersnfs/tulin/mysql-4.1
-
kent@mysql.com authored
into mysql.com:/data0/mysqldev/my/mysql-4.1
-
aelkin@mysql.com authored
fixing encoding example because of table names can not be in koi8r on some platforms.
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1-main
-
tomas@poseidon.ndb.mysql.com authored
- not having lock can cause "block number list" to become corrupt => crash - also may result in 2 threads receiving same block no => possble cause of Bug #13987 Cluster: Loss of data nodes can cause high CPU usage from ndb_mgmd
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1
-
- 15 May, 2006 5 commits
-
-
pekka@mysql.com authored
-
aivanov@mysql.com authored
into mysql.com:/home/alexi/innodb/mysql-4.1-ss29
-
tomas@poseidon.ndb.mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
- invalidate ndb dict cache on cluster disconnect (ClusterMgr.cpp) - add check for correct frm on external lock when table cache is found invalid
-
aivanov@mysql.com authored
Fix BUG#19542 "InnoDB doesn't increase the Handler_read_prev counter.
-
- 14 May, 2006 1 commit
-
-
aelkin@mysql.com authored
fixing names length. Got an issue when merged to 5.0, decided to fix starting from 4.1
-
- 13 May, 2006 1 commit
-
-
aelkin@mysql.com authored
fixing a path to find charset by $MYSQL client. I believe the fix is done what should be by default.
-
- 12 May, 2006 7 commits
-
-
aelkin@mysql.com authored
into mysql.com:/usr_rh9/home/elkin.rh9/MySQL/Merge/4.1
-
aelkin@mysql.com authored
into mysql.com:/usr_rh9/home/elkin.rh9/MySQL/Merge/4.1
-
aelkin@mysql.com authored
A pattern to generate binlog for DROPped temp table in close_temporary_tables was buggy: could not deal with a grave-accent-in-name table. The fix exploits `append_identifier()' for quoting and duplicating accents.
-
kent@mysql.com authored
Change mode to -rw-rw-r-- Ereport.pl, Ecreate.pl, Ecompare.pl: Change mode to -rwxrwxr--
-
kent@mysql.com authored
-
kent@mysql.com authored
Change mode to -rw-rw-r-- dbug_add_tags.pl: Change mode to -rwxrwxr--
-
msvensson@neptunus.(none) authored
- Remove usage of $shrext_cmds variable - Test for libs using all known library file endings
-
- 11 May, 2006 2 commits
-
-
kent@mysql.com authored
Stepped up to 4.0.28
-
tnurnberg@mysql.com authored
into mysql.com:/home/mysql-4.1-10418
-
- 10 May, 2006 2 commits
-
-
kent@mysql.com authored
Compile in all character sets in Max (bug#14918)
-
ramil@mysql.com authored
into mysql.com:/usr/home/ram/work/4.1.b18501
-
- 09 May, 2006 2 commits
-
-
aelkin@mysql.com authored
Binlog lacks encoding info about DROPped temporary table. Idea of the fix is to switch temporary to system_charset_info when a temporary table is DROPped for binlog. Since that is the server, that automatically, but not the client, who generates the query the binlog should be updated on the server's encoding for the coming DROP. The `write_binlog_with_system_charset()' is introduced to replace similar problematic places in the code.
-
mskold@mysql.com authored
-
- 08 May, 2006 2 commits
-
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-4.1
-
tnurnberg@mysql.com authored
load_file() string-function should return NULL rather than throw an error if the file doesn't exist, as per the manual.
-
- 07 May, 2006 3 commits
-
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/mysql-4.1
-
aelkin@mysql.com authored
into mysql.com:/usr_rh9/home/elkin.rh9/MySQL/FIXES/4.1-bug19136_unass_user_var
-
igor@rurik.mysql.com authored
A query with a group by and having clauses could return a wrong result set if the having condition contained a constant conjunct evaluated to FALSE. It happened because the pushdown condition for table with grouping columns lost its constant conjuncts. Pushdown conditions are always built by the function make_cond_for_table that ignores constant conjuncts. This is apparently not correct when constant false conjuncts are present.
-
- 06 May, 2006 3 commits
-
-
sergefp@mysql.com authored
into mysql.com:/home/psergey/mysql-4.1-bug16798
-
kroki@mysql.com authored
into mysql.com:/home/tomash/src/mysql_ab/mysql-4.1-bug16501
-
ingo@mysql.com authored
into mysql.com:/home/mydev/mysql-4.0-bug10405
-