- 03 Sep, 2005 1 commit
-
-
eric@mysql.com authored
Handle systems like default FC4 where 127.0.0.1 doesn't always map to 'localhost' first. (Bug #11822)
-
- 02 Sep, 2005 5 commits
-
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-4.1-clean
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1
-
msvensson@neptunus.(none) authored
-
bar@mysql.com authored
into mysql.com:/usr/home/bar/mysql-4.1.b12363
-
bar@mysql.com authored
into mysql.com:/usr/home/bar/mysql-4.1.b12363
-
- 01 Sep, 2005 20 commits
-
-
lars@mysql.com authored
into mysql.com:/users/lthalmann/bk/mysql-4.1-bug12542
-
joerg@mysql.com authored
-
joerg@mysql.com authored
-
msvensson@neptunus.(none) authored
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1
-
joerg@mysql.com authored
-
lars@mysql.com authored
into mysql.com:/users/lthalmann/bk/mysql-4.1-bug12542
-
lars@mysql.com authored
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/bug11316/my41-bug11316
-
dlenev@mysql.com authored
into mysql.com:/home/dlenev/src/mysql-4.1-bg12423
-
dlenev@mysql.com authored
multi-threaded environment". To avoid deadlocks between several simultaneously run account management commands (particularly between FLUSH PRIVILEGES/SET PASSWORD and GRANT commands) we should always take table and internal locks during their execution in the same order. In other words we should first open and lock privilege tables and only then obtain acl_cache::lock/LOCK_grant locks.
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-4.1
-
kent@mysql.com authored
Make sure mtr_kill_processes() is called with an array ref Corrected error string for STDERR redirect
-
msvensson@neptunus.(none) authored
-
msvensson@neptunus.(none) authored
-
msvensson@neptunus.(none) authored
- Move clearing of expected errors
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-4.1-clean
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-4.1-clean
-
jimw@mysql.com authored
on Windows. (Bug #12325)
-
- 31 Aug, 2005 14 commits
-
-
tomas@poseidon.ndb.mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1
-
tomas@poseidon.ndb.mysql.com authored
-
evgen@moonbone.local authored
into moonbone.local:/work/12861-bug-4.1-mysql
-
tomas@poseidon.ndb.mysql.com authored
-
jimw@mysql.com authored
-
jimw@mysql.com authored
on Solaris even though it is available, and declare it ourselves in that case. (Bug #7156)
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1
-
msvensson@neptunus.(none) authored
Use !<err_no> instead
-
lars@mysql.com authored
rpl_replicate_do.result: New test case sql_parse.cc: All SET statements should be executed by slave thd rpl_replicate_do.test: New test case
-
msvensson@neptunus.(none) authored
- Add stricter checking of syntax in mysqltest
-
kent@mysql.com authored
Backporting from 5.0
-
evgen@moonbone.local authored
Item_func_group_concat::fix_fields() set maybe_null flag to 0, and set it to 1 only if some of it's arguments may be null. When used in subquery in tmp table created field which can't be null. When no data retireved result field have to be set to null and error mentioned in bug report occurs. Also this bug can occur if selecting from not null field in empty table. Function group_concat now marked maybe_null from the very beginning not only if some of it's argument may be null.
-