- 09 Jan, 2007 1 commit
-
-
unknown authored
server The problem was that when memory was exhausted HEAP engine could crash (GROUP BY uses HEAP TABLE). Alternatively, if SET was used, it could report an error "You may only use constant expressions with SET" instead of "Out of memory (Needed NNNNNN bytes)". The solution is: - pass MY_WME to (some) calls to my_malloc() to get correct message. - fix heap_write() so that the first key is skipped during cleanup on ENOMEM because it wasn't inserted and doesn't have to be deleted. No test case is provided because we can't test out-of-memory behaviour in our current test framework. heap/hp_block.c: If allocation fails, write an error message. heap/hp_write.c: On ENOMEM, skip the first key in cleanup, as it wasn't inserted yet. sql/item_func.cc: Add MY_WME so that OOM error will be reported.
-
- 29 Sep, 2006 1 commit
-
-
unknown authored
into chilla.local:/home/mydev/mysql-4.0-bug20719
-
- 28 Sep, 2006 1 commit
-
-
unknown 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. myisam/mi_delete.c: Bug#22384 - DELETE FROM table causes "Incorrect key file for table" Put a negation operator ('!') before _mi_get_last_key() in del(). It returns NULL on error, non-NULL on success.
-
- 27 Sep, 2006 1 commit
-
-
unknown authored
into chilla.local:/home/mydev/mysql-4.0-bug20719
-
- 22 Sep, 2006 3 commits
-
-
unknown authored
"concurrent insert" After merge fix.
-
unknown authored
into chilla.local:/home/mydev/mysql-4.0-bug14400 mysql-test/r/myisam.result: Auto merged myisam/mi_rkey.c: Bug#14400 - Query joins wrong rows from table which is subject of "concurrent insert" Manual merge mysql-test/t/myisam.test: Bug#14400 - Query joins wrong rows from table which is subject of "concurrent insert" Manual merge
-
unknown authored
into chilla.local:/home/mydev/mysql-4.0-bug14400 myisam/mi_rkey.c: Bug#14400 - Query joins wrong rows from table which is subject of "concurrent insert" Manual merge
-
- 07 Sep, 2006 1 commit
-
-
unknown authored
"concurrent insert" Additional fix for full keys and test case. myisam/mi_rkey.c: Bug#14400 - Query joins wrong rows from table which is subject of "concurrent insert" Additional fix for full keys. mysql-test/r/myisam.result: Bug#14400 - Query joins wrong rows from table which is subject of "concurrent insert" Additional results. mysql-test/t/myisam.test: Bug#14400 - Query joins wrong rows from table which is subject of "concurrent insert" Additional test case.
-
- 29 Aug, 2006 1 commit
-
-
unknown authored
subject of "concurrent insert" Better fix by Monty: "The previous bug fix didn't work when using partial keys." mysql-test/r/myisam.result: Bug#14400 - Query joins wrong rows from table which is subject of "concurrent insert" Added test result mysql-test/t/myisam.test: Bug#14400 - Query joins wrong rows from table which is subject of "concurrent insert" Added test case
-
- 10 Aug, 2006 1 commit
-
-
unknown authored
Better bug fix for #14400 "Query joins wrong rows from table which is subject of "concurrent insert"" The previous bug fix didn't work when using partial keys. Don't use GNUC min/max operations are they are depricated. Fixed valgrind warning BitKeeper/etc/ignore: Added */.libs/* include/my_global.h: Don't use GNUC min/max operations are they are depricated myisam/mi_rkey.c: Better bug fix for #14400 "Query joins wrong rows from table which is subject of "concurrent insert"" The previous bug fix didn't work when using partial keys. myisam/mi_test_all.res: Updated results to match mi_test_all.sh myisam/mi_test_all.sh: Removed confusing warning mysql-test/r/myisam.result: Added test case for #14400 mysql-test/t/myisam.test: Added test case for #14400 sql/sql_select.cc: Fixed valgrind warning (in field_string::val_int())
-
- 29 Jul, 2006 1 commit
-
-
unknown authored
Corrected typo configure.in: Corrected typo
-
- 28 Jul, 2006 3 commits
-
-
unknown authored
Man page for mysqld command move to section 8 (bug#21220) configure.in: Man page for mysqld command move to section 8 (bug#21220) man/Makefile.am: Man page for mysqld command move to section 8 (bug#21220)
-
unknown authored
Man page for "mysqld" command move to section 8 (bug#21220) scripts/make_binary_distribution.sh: Man page for "mysqld" command move to section 8 (bug#21220)
-
unknown authored
Man page for "mysqld" command move to section 8 (bug#21220) support-files/mysql.spec.sh: Man page for "mysqld" command move to section 8 (bug#21220)
-
- 24 Jul, 2006 1 commit
-
-
unknown authored
Filter out strange control characters, messes up logs netware/BUILD/mwasmnlm: Filter out strange control characters, messes up logs netware/BUILD/mwccnlm: Filter out strange control characters, messes up logs netware/BUILD/mwldnlm: Filter out strange control characters, messes up logs
-
- 21 Jul, 2006 1 commit
-
-
unknown authored
Fixed a possible problem with reading of dynamic records when a write cache is active. The cache must be flushed whenever a part of the file in the write cache is to be read. Added a read optimization to _mi_read_dynamic_record(). No test case. This was a hypothetical but existing problem. myisam/mi_dynrec.c: Bug#20719 - Reading dynamic records with write buffer could fail Fixed a possible problem with reading of dynamic records when a write cache is active. The cache must be flushed whenever a part of the file in the write cache is to be read. This must be done before the read of the header and before the read of the rest block. Renamed the 'flag' and 'skipp_deleted_blocks' variables. Added a read optimization to _mi_read_dynamic_record() that was present in _mi_read_rnd_dynamic_record() already. After _mi_get_block_info() we have some bytes of the record in the header buffer already. No need to read them again.
-
- 08 Jul, 2006 1 commit
-
-
unknown authored
into chilla.local:/home/mydev/mysql-4.0-bug14400
-
- 07 Jul, 2006 2 commits
- 05 Jul, 2006 1 commit
-
-
unknown authored
-
- 01 Jul, 2006 1 commit
-
-
unknown authored
On exactly-sized Strings, the String::c_ptr() function peeked beyond the end of the buffer, possibly into unititialized space to see whether the buffer was NUL-terminated. In a place that did peek improperly, we now use a c_ptr_safe() function, which doesn't peek where it shouldn't. client/sql_string.h: Back-port String::c_ptr_safe(). sql/item_func.h: Describe side-effect behavior. sql/item_strfunc.cc: Use the "_safe" version of c_ptr to avoid looking for a terminating NUL character outside the initialized memory area. Valgrind hates it when one does that, and it theoretically could lead to a SEGV. sql/sql_string.h: Back-port String::c_ptr_safe().
-
- 28 Jun, 2006 1 commit
-
-
unknown authored
It was possible that fetching a record by an exact key value (including the record pointer) could return a record with a different key value. This happened only if a concurrent insert added a record with the searched key value after the fetching statement locked the table for read. The search succeded on the key value, but the record was rejected as it was past the file length that was remembered at start of the fetching statement. With other words it was rejected as being a concurrently inserted record. The action to recover from this problem was to fetch the record that is pointed at by the next key of the index. This was repeated until a record below the file length was found. I do now avoid this loop if an exact match was searched. If this match is beyond the file length, it is now treated as "key not found". There cannot be another key with the same record pointer. myisam/mi_rkey.c: Bug#14400 - Query joins wrong rows from table which is subject of "concurrent insert" Added a check for exact key match before searching for the next key that was not concurrently inserted. If an exact key match finds a concurrently inserted row, this must be treated as "key not found". sql/sql_class.cc: Bug#14400 - Query joins wrong rows from table which is subject of "concurrent insert" Fixed some DBUG_ENTER strings.
-
- 27 Jun, 2006 1 commit
-
-
unknown authored
-
- 26 Jun, 2006 1 commit
-
-
unknown authored
For compatibility, don't use {..,..} in pattern matching make_binary_distribution.sh: Added .dylib and .sl as shared library extensions scripts/make_binary_distribution.sh: Added .dylib and .sl as shared library extensions scripts/make_sharedlib_distribution.sh: For compatibility, don't use {..,..} in pattern matching
-
- 13 Jun, 2006 1 commit
-
-
unknown authored
mysql-test/r/func_str.result: Fix for bug #12728: Very strange behaviour of ELT - test case mysql-test/t/func_str.test: Fix for bug #12728: Very strange behaviour of ELT - test result sql/item_strfunc.cc: Fix for bug #12728: Very strange behaviour of ELT - Item_func_elt::eq() introduced: check 'item' member as well (to distinguish for instance elt(1, 'a', 'b') and elt(2, 'a', 'b') sql/item_strfunc.h: Fix for bug #12728: Very strange behaviour of ELT - Item_func_elt::eq() introduced: check 'item' member as well (to distinguish for instance elt(1, 'a', 'b') and elt(2, 'a', 'b')
-
- 20 May, 2006 1 commit
-
-
unknown authored
Always compile position independent support-files/mysql.spec.sh: Always compile position independent
-
- 12 May, 2006 1 commit
-
-
unknown authored
Change mode to -rw-rw-r-- dbug_add_tags.pl: Change mode to -rwxrwxr-- dbug/dbug_add_tags.pl: Change mode to -rwxrwxr-- myisammrg/myrg_range.c: Change mode to -rw-rw-r-- mysql-test/r/innodb_handler.result: Change mode to -rw-rw-r-- mysql-test/r/repair.result: Change mode to -rw-rw-r-- mysql-test/std_data/master-bin.001: Change mode to -rw-rw-r-- mysql-test/std_data/trunc_binlog.001: Change mode to -rw-rw-r-- mysql-test/t/bulk_replace.test: Change mode to -rw-rw-r-- mysql-test/t/create_select_tmp.test: Change mode to -rw-rw-r-- mysql-test/t/ctype_tis620.test: Change mode to -rw-rw-r-- mysql-test/t/handler.test: Change mode to -rw-rw-r-- mysql-test/t/innodb_handler.test: Change mode to -rw-rw-r-- mysql-test/t/mix_innodb_myisam_binlog-master.opt: Change mode to -rw-rw-r-- mysql-test/t/repair.test: Change mode to -rw-rw-r-- mysql-test/t/rpl_commit_after_flush.test: Change mode to -rw-rw-r-- mysql-test/t/rpl_free_items-slave.opt: Change mode to -rw-rw-r-- mysql-test/t/rpl_free_items.test: Change mode to -rw-rw-r-- scripts/mysql_secure_installation.sh: Change mode to -rw-rw-r-- sql/sql_handler.cc: Change mode to -rw-rw-r-- support-files/mysql-multi.server.sh: Change mode to -rw-rw-r--
-
- 11 May, 2006 1 commit
-
-
unknown authored
Stepped up to 4.0.28 configure.in: Stepped up to 4.0.28
-
- 06 May, 2006 1 commit
-
-
unknown authored
into mysql.com:/home/mydev/mysql-4.0-bug10405
-
- 04 May, 2006 1 commit
-
-
unknown authored
Delete: Docs/changelog-4.0.xml BitKeeper/deleted/.del-changelog-4.0.xml~8f56ee8a913e848b: Delete: Docs/changelog-4.0.xml
-
- 25 Apr, 2006 2 commits
- 11 Apr, 2006 3 commits
- 10 Apr, 2006 3 commits
-
-
unknown authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-4.0
-
unknown authored
code. (Bug #13621) configure.in: Test whether atomic_add() and atomic_sub() are available in C++ code, since that is primarily where we will be using them.
-
unknown authored
Whenever 'myisamchk' needed to recreate a table, the auto increment information was lost. Now the forgotten element of the table creation information is set correctly. myisam/mi_check.c: Bug#10405 - myisamchk damages auto_increment columns when changing character set Added some DBUG statements. Enabled 'with_auto_increment' in 'create_info' when recreating a table.
-
- 08 Apr, 2006 1 commit
-
-
unknown authored
acinclude.m4: Check tinfo library presence and use it.
-
- 07 Apr, 2006 1 commit
-
-
unknown authored
mysql-test/mysql-test-run.sh: Provide info about the options used for this run to any evaluation tool.
-