An error occurred fetching the project authors.
- 04 Oct, 2006 1 commit
-
-
msvensson@neptunus.(none) authored
Update tests and result files after running with new mysqltest that better detects problems with test files
-
- 03 Oct, 2006 1 commit
-
-
msvensson@shellback.(none) authored
- ie. backport from 5.1 - also update testcase error dected by new version
-
- 22 Dec, 2005 1 commit
-
-
lars@mysql.com authored
This includes both code and test cases.
-
- 12 Apr, 2005 2 commits
-
-
serg@serg.mylan authored
correct result after bugfix sql/sql_class.cc initialize net.query_cache_query
-
serg@serg.mylan authored
-
- 17 Dec, 2004 1 commit
-
-
guilhem@mysql.com authored
Fix for BUG#7358: removing warning reporting of mysqldump 4.1.8 when calling SHOW CREATE DATABASE, as we deal almost gracefully with it (back to behaviour of 4.1.7). Warning was not fatal: mysqldump continued. And the good thing is that it helped spot that starting from 4.1.7, SHOW CREATE DATABASE failed (if --single-transaction and first db has non-empty InnoDB table and there is a second db) and thus mysqldump produced CREATE DATABASE statements missing the CHARACTER SET clause. Removing the bug which was in the server, and the warning reporting in mysqldump (compatibility with old servers).
-
- 30 Nov, 2004 1 commit
-
-
guilhem@mysql.com authored
two-line fix for BUG#6732 "FLUSH TABLES WITH READ LOCK + COMMIT makes next FLUSH...LOCK hang forever" (originally reported as "second run of innobackup hangs forever and can even hang server"). Plus testcase for the bugfix and comments about global read locks.
-
- 20 Aug, 2004 2 commits
-
-
serg@serg.mylan authored
-
guilhem@mysql.com authored
in a deadlock-free manner. This splits locking the global read lock in two steps. This fixes a consequence of this bug, known as: BUG#4953 'mysqldump --master-data may report incorrect binlog position if using InnoDB' And a test.
-