- 14 Feb, 2005 3 commits
-
-
heikki@hundin.mysql.fi authored
into hundin.mysql.fi:/home/heikki/mysql-5.0
-
gluh@gluh.mysql.r18.ru authored
Can't repeat information_schema test failure Fix for lowercase_table3 only
-
heikki@hundin.mysql.fi authored
Fix a glitch reported by Guilhem: release the memory allocated for innodb_internal_... if innobase_init() fails; cleanups: in ha_innodb, you should use the InnoDB formatting style for the source code
-
- 13 Feb, 2005 2 commits
-
-
heikki@hundin.mysql.fi authored
Fix memory corruption bug reported by Georg Richter: if one created a table whose primary key contained at least 2 column prefixes, that could corrupt the memory heap of prebuilt_t
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.0-compile
-
- 12 Feb, 2005 2 commits
-
-
hf@deer.(none) authored
into deer.(none):/home/hf/work/mysql-5.0.clean
-
hf@deer.(none) authored
-
- 11 Feb, 2005 11 commits
-
-
marko@hundin.mysql.fi authored
into hundin.mysql.fi:/home/marko/mysql-5.0
-
joerg@mysql.com authored
-
ingo@mysql.com authored
-
ingo@mysql.com authored
-
ingo@mysql.com authored
into mysql.com:/home/mydev/mysql-4.1-bug8306
-
joerg@mysql.com authored
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-4.1-0
-
igor@rurik.mysql.com authored
Adjusted results of the test case for bug #7520 for 4.1.
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-4.1-0
-
igor@rurik.mysql.com authored
Added a test case for bug #7520. table.cc: Fixed bug #7520. The bug was caused by a wrong calculation of the field max_key_length for a TABLE structure when there was an index on a blob field.
-
brian@zim.(none) authored
Set of fixes requested by Kent in IRC. Tested (except the windows changes since I am trusting Kent...). No windows compiles here folks...
-
- 10 Feb, 2005 22 commits
-
-
jimw@mysql.com authored
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-4.0-clean
-
lars@mysql.com authored
-
lars@mysql.com authored
binlog-do-db or binlog-ignore-db are in effect. (In the future 5.1? 5.0? I think each statement should be verified against the filtering criteria based on the database it *uses* and not the *current* one. But, right now the *current* database is what counts according to the semantics of the manual.)
-
mats@mysql.com authored
into mysql.com:/home/bk/b7853-mysql-5.0
-
ingo@mysql.com authored
It was a thread stack overrun. IA64 had its own stack size section already. Enlarged its default stack size from 192K to 256K.
-
konstantin@mysql.com authored
into mysql.com:/home/kostja/work/mysql-5.0-root
-
konstantin@mysql.com authored
-
konstantin@mysql.com authored
into mysql.com:/home/kostja/work/mysql-5.0-root
-
konstantin@mysql.com authored
-
konstantin@mysql.com authored
reset mysql->net.last_error": the solution is to clear MYSQL->net error before performing COM_CLOSE: if the call succeeds, the connection is usable for other statements. More comprehensive fix is to clear MYSQL->net for all recoverable errors at the time they happen, it will be implemented in 5.0 as it introduces incompatibility in behavior.
-
konstantin@mysql.com authored
-
msvensson@neptunus.homeip.net authored
into neptunus.homeip.net:/home/msvensson/mysql/mysql-5.0
-
monty@mysql.com authored
After merge fixes Don't give duplicate warnings for some ::store() functions
-
joerg@mysql.com authored
-
joerg@mysql.com authored
it also works on file names with special characters.
-
msvensson@neptunus.homeip.net authored
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-5.0
-
konstantin@mysql.com authored
-
pem@mysql.comhem.se authored
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-4.1-clean
-
monty@mysql.com authored
-