An error occurred fetching the project authors.
- 20 Apr, 2006 5 commits
-
-
mleich@mysql.com authored
into three.local.lan:/home/matthias/Arbeit/mysql-5.0/src-1
-
evgen@moonbone.local authored
Remove duplicate test case for bug#14169
-
igor@rurik.mysql.com authored
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-
- 19 Apr, 2006 8 commits
-
-
igor@rurik.mysql.com authored
Temporarily commented out a query from the test case for bug 14169 to make it pass with --ps-protocol.
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-4.1-2
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.0-clean
-
evgen@moonbone.local authored
into moonbone.local:/work/14169-bug-4.1-mysql
-
evgen@moonbone.local authored
Corrected test case for the bug#14169 to make it pass in --ps-protocol mode.
-
svoj@april.(none) authored
After a locking error the open table(s) were not fully cleaned up for reuse. But they were put into the open table cache even before the lock was tried. The next statement reused the table(s) with a wrong lock type set up. This tricked MyISAM into believing that it don't need to update the table statistics. Hence CHECK TABLE reported a mismatch of record count and table size. Fortunately nothing worse has been detected yet. The effect of the test case was that the insert worked on a read locked table. (!) I added a new function that clears the lock type from all tables that were prepared for a lock. I call this function when a lock failes. No test case. One test would add 50 seconds to the test suite. Another test requires file mode modifications. I added a test script to the bug report. It contains three cases for failing locks. All could reproduce a table corruption. All are fixed by this patch. This bug was not lock timeout specific.
-
stewart@mysql.com authored
into mysql.com:/home/stewart/Documents/MySQL/5.0/merge
-
igor@rurik.mysql.com authored
The bug caused a reported index corruption in the cases when key_cache_block_size was not a multiple of myisam_block_size, e.g. when key_cache_block_size=1536 while myisam_block_size=1024.
-
- 18 Apr, 2006 4 commits
-
-
mleich@mysql.com authored
into mysql.com:/home/matthias/Arbeit/mysql-5.0/src-1
-
stewart@mysql.com authored
into mysql.com:/home/stewart/Documents/MySQL/5.0/merge
-
stewart@mysql.com authored
into mysql.com:/home/stewart/Documents/MySQL/4.1/merge
-
stewart@mysql.com authored
into mysql.com:/home/stewart/Documents/MySQL/4.1/merge
-
- 17 Apr, 2006 5 commits
-
-
cmiller@zippy.(none) authored
into zippy.(none):/home/cmiller/work/mysql/mysql-5.0__ready
-
cmiller@zippy.(none) authored
into zippy.(none):/home/cmiller/work/mysql/mysql-5.0__ready
-
gkodinov@mysql.com authored
Testsuite added
-
bar@mysql.com authored
5.0 additional fix for b#18691 Handle DECIMAL the same with INT and REAL.
-
bar@mysql.com authored
into mysql.com:/usr/home/bar/mysql-5.0
-
- 16 Apr, 2006 1 commit
-
-
cmiller@zippy.(none) authored
does not have "NOT NULL" attribute set. Also, calculate the padding characters more safely, so that a negative number doesn't cause it to print MAXINT-n spaces.
-
- 15 Apr, 2006 1 commit
-
-
svoj@april.(none) authored
into april.(none):/home/svoj/devel/mysql/BUG17917/mysql-5.0
-
- 14 Apr, 2006 3 commits
-
-
evgen@moonbone.local authored
into moonbone.local:/work/14169-bug-4.1-mysql
-
aelkin@mysql.com authored
removing comments from the opt file.
-
bar@mysql.com authored
into mysql.com:/usr/home/bar/mysql-4.1.b18691
-
- 13 Apr, 2006 13 commits
-
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-5.0
-
konstantin@mysql.com authored
into mysql.com:/opt/local/work/mysql-5.0-runtime-merge
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-5.0
-
bell@sanja.is.com.ua authored
-
konstantin@mysql.com authored
into mysql.com:/opt/local/work/mysql-5.0-runtime-merge
-
mleich@mysql.com authored
into three.local.lan:/home/matthias/Arbeit/mysql-5.0/src-1
-
aelkin@dl145j.mysql.com authored
into dl145j.mysql.com:/tmp/andrei/5.0-bug18715_drop_view_slave
-
mleich@mysql.com authored
MySQL 4.1 and Bug#16920 rpl_deadlock_innodb fails in show slave status (reported for MySQL 5.1) - backport of several fixes done in MySQL 5.0 to 4.1 - fix for new discovered instability (see comment on Bug#12429 + Bug#16920) - reenabling of testcases
-
bell@sanja.is.com.ua authored
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-5.0
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-5.0
-
grog@mysql.com authored
into mysql.com:/home/MySQL/5.0-Bug-17248a
-
sergefp@mysql.com authored
into mysql.com:/home/psergey/mysql-5.0-csc9139
-