- 27 Jun, 2005 4 commits
-
-
unknown authored
up CREATE TABLE in innodb_file_per_table=1 mode. innobase/fil/fil0fil.c: fil_extend_space_to_desired_size(): Do not allocate or initialize more memory than is necessary. Write at most one megabyte at a time. innobase/include/os0file.h: os_file_set_size(): Corrected the synopsis innobase/os/os0file.c: os_file_set_size(): Corrected the synopsis and some comments. s/offset/current_size; s/low/desired_size/; Do not allocate or initialize more memory than is necessary. Write at most one megabyte at a time.
-
unknown authored
-
unknown authored
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1
-
- 24 Jun, 2005 3 commits
-
-
unknown authored
Moved the key statistics update to info(). The table is not locked in open(). This made wrong stats possible. No test case for the test suite. This happens only with heavy concurrency. A test script is added to the bug report. mysql-test/r/heap_hash.result: Bug#10178 - failure to find a row in heap table by concurrent UPDATEs Updated test results to reflect the new statistics behaviour. mysql-test/t/heap_hash.test: Bug#10178 - failure to find a row in heap table by concurrent UPDATEs Added a FLUSH TABLES to avoid statistics differences between normal and ps-protocol tests. sql/ha_heap.cc: Bug#10178 - failure to find a row in heap table by concurrent UPDATEs Moved the key statistics update to info(). The table is not locked in open(). This made wrong stats possible. sql/ha_heap.h: Bug#10178 - failure to find a row in heap table by concurrent UPDATEs Added an element to track the validity of the key statistics.
-
unknown authored
-
unknown authored
include/my_global.h: an improvement (bug #7851: C++ 'new' conflicts with kernel header asm/system.h). redefine 'new' before #include <asm/atomic.h> in any case.
-
- 23 Jun, 2005 16 commits
-
-
unknown authored
into mysql.com:/home/timka/mysql/src/4.1-virgin
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1
-
unknown authored
into mysql.com:/home/timka/mysql/src/4.1-virgin
-
unknown authored
into mysql.com:/Users/kent/mysql/bk/mysql-4.1
-
unknown authored
into mysql.com:/home/psergey/mysql-4.1-bug10151
-
unknown authored
Fix for fix for bug #9728 Error caused server hang on prepared insert ... select sql/sql_parse.cc: Fix for fix for bug #9728 Error caused server hang on prepared insert ... select
-
unknown authored
Might need a restart after test with special TZ Removed unused argument to run_mysqltest() mysql-test/mysql-test-run.pl: Might need a restart after test with special TZ Removed unused argument to run_mysqltest()
-
unknown authored
into mysql.com:/home/psergey/mysql-4.1-bug10151
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1
-
unknown authored
into mysql.com:/home/timka/mysql/src/4.1-virgin
-
unknown authored
into mysql.com:/space/my/mysql-4.1
-
unknown authored
-
unknown authored
BitKeeper/deleted/.del-generate-flag-images~f77476753fff8186: Delete: Docs/Support/generate-flag-images Docs/Makefile.am: - fixed node names for the new info file Docs/Support/generate-text-files.pl: - stop printing if the index was reached
-
unknown authored
into mysql.com:/home/psergey/mysql-4.1-bug10151
-
unknown authored
into mysql.com:/home/timka/mysql/src/4.1-bug-11185
-
unknown authored
The source of the problem is in Field_longlong::cmp. If 'this' is an unsigned number, the method casts both the current value, and the constant that we compare with to an unsigned number. As a result if the constant we compare with is a negative number, it wraps to some unsigned number, and the comparison is incorrect. When the optimizer chooses the "range" access method, this problem causes handler::read_range_next to reject the current key when the upper bound key is a negative number because handler::compare_key incorrectly considers the positive and negative keys to be equal. The current patch does not correct the source of the problem in Field_longlong::cmp because it is not easy to propagate sign information about the constant at query execution time. Instead the patch changes the range optimizer so that it never compares unsiged fields with negative constants. As an added benefit, queries that do such comparisons will execute faster because the range optimizer replaces conditions like: (a) (unsigned_int [< | <=] negative_constant) == FALSE (b) (unsigned_int [> | >=] negative_constant) == TRUE with the corresponding constants. In some cases this may even result in constant time execution. mysql-test/r/range.result: - Changed incorrect result of an old test - Added new results for BUG#11185 mysql-test/t/range.test: - Added new tests for BUG#11185 - Deleted an old comment because now the problem is fixed sql/opt_range.cc: Added a new optimization to the range optimizer where we detect that an UNSIGNED field is compared with a negative constant. Depending on the comparison operator, we know directly that the result of the comparison is either TRUE or FALSE for all input values, and we need not check each value. This optimization is also necessary so that the index range access method produces correct results when comparing unsigned fields with negative constants.
-
- 22 Jun, 2005 15 commits
-
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1 sql/sql_base.cc: Auto merged
-
unknown authored
-
unknown authored
into mysql.com:/home/psergey/mysql-4.1-bug10151
-
unknown authored
into mdk10.(none):/home/reggie/bk/bug9148
-
unknown authored
into moonbone.local:/work/mysql-4.1-bug-8147
-
unknown authored
Fix for fix for bug#9728 decreased functionality in "on duplicate key update" Have to return false to set flag for whole expression. sql/item.h: Fix for fix for bug#9728 decreased functionality in "on duplicate key update" Have to return false to set flag for whole expression.
-
unknown authored
client/mysqldump.c: Fix progname of mysqldump mysql-test/r/mysqldump.result: Update test results mysql-test/t/mysqldump.test: Update tests, no need for results
-
unknown authored
- Importing the bug fixes by patch due to merge problems. client/mysqldump.c: Import patch patch mysql-test/r/mysqldump.result: Import patch patch mysql-test/t/mysqldump.test: Import patch patch
-
unknown authored
mysql-test/r/rpl_multi_update3.result: Added test cases mysql-test/t/rpl_multi_update3.test: Added test cases
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/bug10589
-
unknown authored
into mysql.com:/space/my/mysql-4.1
-
unknown authored
into mysql.com:/usr/local/home/marty/MySQL/mysql-4.1
-
unknown authored
ndb/src/common/util/version.c: Maybe upgrade compatibility in 4.1 range to latest build version
-
unknown authored
mysql-test/README: fix README file to be more verbose match actual situation
-
unknown authored
Remove changes made by bug fix #8147. They strips list of insert_table_list to only insert table, which results in error reported in bug #9728. Added flag to Item to resolve ambigous fields reported in bug #8147. sql/item.h: Fix bug#9728 decreased functionality in "on duplicate key update". sql/item.cc: Fix bug#9728 decreased functionality in "on duplicate key update" sql/sql_parse.cc: Fix bug#9728 decreased functionality in "on duplicate key update" sql/sql_base.cc: Fix bug#9728 decreased functionality in "on duplicate key update". sql/sql_yacc.yy: Fix bug#9728 decreased functionality in "on duplicate key update" mysql-test/t/insert_select.test: Test case for bug#9728 Decreased functionality in "on duplicate key update". mysql-test/r/insert_select.result: Test case for bug#9728 Decreased functionality in "on duplicate key update".
-
- 21 Jun, 2005 2 commits
-
-
unknown authored
mysql-test/r/rpl_multi_update3.result: Changes from code review mysql-test/t/rpl_multi_update3.test: Changes from code review sql/sql_parse.cc: Changes from code review
-
unknown authored
my_access.c: Fixed problem where in some cases check_if_legal_filename was returning 0 for illegal names mysys/my_access.c: Fixed problem where in some cases check_if_legal_filename was returning 0 for illegal names
-