- 29 Sep, 2006 2 commits
-
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0-bug20627
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0-bug22384
-
- 28 Sep, 2006 11 commits
-
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0-bug22384
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-4.1-bug22384
-
svoj@mysql.com/april.(none) authored
into mysql.com:/home/svoj/devel/mysql/BUG21617/mysql-5.0-engines
-
svoj@mysql.com/april.(none) authored
into mysql.com:/home/svoj/devel/mysql/BUG21617/mysql-4.1-engines
-
svoj@mysql.com/april.(none) authored
Crash may happen when selecting from a merge table that has underlying tables with less indexes than in a merge table itself. If number of keys in merge table is not bigger than requested key number, return error.
-
svoj@mysql.com/april.(none) authored
into mysql.com:/home/svoj/devel/mysql/BUG21675/mysql-5.0-engines
-
svoj@mysql.com/april.(none) authored
into mysql.com:/home/svoj/devel/mysql/BUG21675/mysql-5.0-engines
-
svoj@mysql.com/april.(none) authored
If mysqld is linked against system installed zlib (which is likely compiled w/o LFS) and archive table exceedes 2G, mysqld will likely be terminated with SIGXFSZ. Prior to actual write perform a check if there is space in data file. This fixes abnormal process termination with SIGXFSZ. No test case for this bugfix.
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-4.1-bug20719-m
-
istruewing@chilla.local authored
Deletes on a big index could crash the index when it needs to shrink. Put a forgotten negation operator in. No test case. It is too big for the test suite. And it does not work with 4.0, only with higher versions. It is attached to the bug report.
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0-bug20719-m
-
- 27 Sep, 2006 7 commits
-
-
svoj@mysql.com/april.(none) authored
-
svoj@mysql.com/april.(none) authored
into mysql.com:/home/svoj/devel/mysql/merge/mysql-5.0-engines
-
svoj@mysql.com/april.(none) authored
into mysql.com:/home/svoj/devel/mysql/merge/mysql-4.1-engines
-
svoj@mysql.com/april.(none) authored
into mysql.com:/home/svoj/devel/mysql/merge/mysql-5.0-engines
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0-bug20719-m
-
istruewing@chilla.local authored
After merge fix.
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-4.1-bug20719-m
-
- 23 Sep, 2006 2 commits
-
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0-bug14400-monty
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-4.1-bug14400-monty
-
- 22 Sep, 2006 3 commits
-
-
istruewing@chilla.local authored
"concurrent insert" After merge fix.
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-4.0-bug14400
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-4.0-bug14400
-
- 21 Sep, 2006 1 commit
-
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0-toteam
-
- 20 Sep, 2006 3 commits
-
-
svoj@mysql.com/april.(none) authored
This problem affects myisam_ftdump tool only. For fulltext index positive subkeys means word weight, negative subkeys means number of documents in level 2 fulltext index. Fixed that document counter was not properly updated for keys having level 2 fulltext index. No test case for this bug.
-
istruewing@chilla.local authored
Bug#20627 - INSERT DELAYED does not honour auto_increment_* variables INSERT DELAYED ignored an explicitly set INSERT_ID and session specific auto_increment_* variables. The problem was that the inserts are done by a system thread, which does not have access to the session variables of the user thread. On a proposal of Guilhem I fixed it so that the variables are copied to the data structure for every delayed row. The system thread sets its session variables from these values.
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-4.1-bug14400-monty
-
- 19 Sep, 2006 5 commits
-
-
svoj@mysql.com/april.(none) authored
Fixed confusing error message from the storage engine when it fails to open underlying table. The error message is issued when a table is _opened_ (not when it is created).
-
istruewing@chilla.local authored
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0-bug14400-monty
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-4.1-bug14400-monty
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0--team
-
- 18 Sep, 2006 6 commits
-
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0--team
-
svoj@may.pils.ru authored
into may.pils.ru:/home/svoj/devel/mysql/merge/mysql-4.1-engines
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data/bk/team_tree_merge/MERGE/mysql-5.0-opt
-
svoj@april.(none) authored
into april.(none):/home/svoj/devel/mysql/merge/mysql-5.0-engines
-
svoj@april.(none) authored
into april.(none):/home/svoj/devel/mysql/merge/mysql-5.0-engines
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data/bk/team_tree_merge/MERGE/mysql-5.0-opt
-