- 09 May, 2008 4 commits
-
-
unknown authored
Missing file: include/is_embedded.inc This file was left out of the initial changeset by misstake. mysql-test/include/is_embedded.inc: Missing file patch: include/is_embedded.inc
-
unknown authored
into adventure.(none):/home/thek/Development/cpp/mysql-5.1-bugteam
-
unknown authored
The event scheduler was not designed to work in embedded mode. This patch disables and excludes the event scheduler when the server is compiled for embedded build. libmysqld/Makefile.am: Reduce the amount of event code in an embedded build. mysql-test/t/events_trans.test: Disable test if run in embedded mode. sql/Makefile.am: Introduce definition HAVE_EVENT_SCHEDULER and one new source file. sql/event_data_objects.cc: Refactor Event_parse_data to new file. sql/event_data_objects.h: Refactor Event_parse_data to new file. Move global definitions to new file. sql/event_queue.cc: Move all parsed items to Event_parse_data for easier modularization. sql/events.cc: Move all parsed items to Event_parse_data for easier modularization. sql/mysqld.cc: Disable the event schedular subsystem if the server is compiled in embedded mode. sql/set_var.cc: Disable the event schedular subsystem if the server is compiled in embedded mode. sql/set_var.h: Disable the event schedular subsystem if the server is compiled in embedded mode. sql/sql_db.cc: Disable the event schedular subsystem if the server is compiled in embedded mode. sql/sql_parse.cc: Disable the event schedular subsystem if the server is compiled in embedded mode. sql/sql_show.cc: Disable the event schedular subsystem if the server is compiled in embedded mode. sql/sql_test.cc: Disable the event schedular subsystem if the server is compiled in embedded mode. sql/sql_yacc.yy: Only include event-code needed for parsing to reduce impact on embedded build. Move all constants to Event_parse_data class. mysql-test/r/events_embedded.result: Add test case to make sure the 'event_scheduler' can't be activated in embedded mode. mysql-test/r/is_embedded.require: Add test case to make sure the 'event_scheduler' can't be activated in embedded mode. mysql-test/t/events_embedded.test: Add test case to make sure the 'event_scheduler' can't be activated in embedded mode. sql/event_parse_data.cc: New file. Extracted Event_parse data into a new file. sql/event_parse_data.h: New file. Extracted Event_parse data into a new file.
-
unknown authored
Remove optimizations on innobase/mem/* to avoid apparent compiler bug which causes memory overruns. See also bug 19424, and probably bug 36366. This is done in 5.1+; 5.0 already has this workaround in place. storage/innobase/CMakeLists.txt: Remove optimizations on innobase/mem/* to avoid apparent compiler bug which causes memory overruns. See bug 34297, bug 19424, and probably bug 36366.
-
- 08 May, 2008 4 commits
-
-
unknown authored
test change for 5.1+ (show create view adds two columns in 5.1) Patch only for 5.1+ mysql-test/suite/rpl/r/rpl_sp.result: restored the original 5.1 test result mysql-test/suite/rpl/r/rpl_view.result: Bug#32575: Parse error of stmt with extended comments on slave side Updated test result for show create view in 5.0 to 5.1
-
unknown authored
into client-10-129-10-147.upp.off.mysql.com:/Users/mattiasj/clones/topush-51-bugteam mysql-test/suite/rpl/r/rpl_sp.result: Auto merged mysql-test/suite/rpl/t/rpl_view.test: Auto merged sql/sql_view.cc: This was already fixed in 5.1 mysql-test/suite/rpl/r/rpl_view.result: manual merge
-
unknown authored
into client-10-129-10-147.upp.off.mysql.com:/Users/mattiasj/clones/topush-50-bugteam
-
unknown authored
Problem was that mysql_create_view did not remove all comments characters when writing to binlog, resulting in parse error of stmt on slave side. Solution was to use the recreated select clause and add a generated CHECK OPTION clause if needed. mysql-test/r/rpl_sp.result: Bug#32575 - Parse error of stmt with extended comments on slave side Updated test result mysql-test/r/rpl_view.result: Bug#32575 - Parse error of stmt with extended comments on slave side Updated test result mysql-test/t/rpl_view.test: Bug#32575 - Parse error of stmt with extended comments on slave side Added test case sql/sql_view.cc: Bug#32575 - Parse error of stmt with extended comments on slave side Problem was that mysql_create_view did not remove all comments characters when writing to binlog, resulting in parse error of stmt on slave side. Solution was to use the recreated select clause and generate 'WITH {LOCAL|CASCADED} CHECK OPTION'.
-
- 07 May, 2008 6 commits
-
-
unknown authored
into mysql.com:/Users/davi/mysql/mysql-5.1-bugteam
-
unknown authored
into riska.(none):/home/sven/bkroot/5.1-bugteam mysql-test/suite/rpl/t/disabled.def: Auto merged
-
unknown authored
Temporarily checking in an incorrect test case. Rationale: the impact of this bug is negligible (it's almost a feature request). We need 5.1 to be stable, and making a real fix is a bit risky. So the fix is postponed to 6.0. mysql-test/suite/rpl/r/rpl_ddl.result: Updated result file. mysql-test/suite/rpl/t/disabled.def: Enabling test case rpl_ddl.test
-
unknown authored
The test suite/rpl/t/rpl_innodb_bug28430.test was disabled because of BUG#32247, but not re-enabled when BUG#32247 was fixed. I've re-enabled it. The test and result file needed to be updated too. mysql-test/suite/rpl/r/rpl_innodb_bug28430.result: Updated result file. mysql-test/suite/rpl/t/disabled.def: Enabled the rpl_innodb_bug28430 test case. mysql-test/suite/rpl/t/rpl_innodb_bug28430.test: show slave status is not needed since we have select count(*)
-
unknown authored
- Disable the "prefer full scan on clustered primary key over full scan of any secondary key" rule introduced by BUG#35850. - Update test results accordingly (bk trigger: file this for BUG#35850) mysql-test/r/innodb.result: BUG#35850 "Performance regression in 5.1.23/5.1.24" - Update test results mysql-test/r/innodb_mysql.result: BUG#35850 "Performance regression in 5.1.23/5.1.24" - Testcase - Update test results mysql-test/r/join_outer_innodb.result: BUG#35850 "Performance regression in 5.1.23/5.1.24" - Update test results mysql-test/t/innodb_mysql.test: BUG#35850 "Performance regression in 5.1.23/5.1.24" - Testcase sql/sql_select.cc: BUG#35850 "Performance regression in 5.1.23/5.1.24" - Disable the "prefer full scan on clustered primary key over full scan of any secondary key" rule introduced by BUG#35850.
-
unknown authored
has been fixed and closed. mysql-test/t/disabled.def: Re-enable test case as bug has been fixed.
-
- 06 May, 2008 10 commits
-
-
unknown authored
into mysql.com:/Users/davi/mysql/mysql-5.1-bugteam
-
unknown authored
into mysql.com:/Users/davi/mysql/mysql-5.1-bugteam
-
unknown authored
The problem is that the patch for Bug 33464 didn't update the results of the test cases which caused the problem. Dropping a stored routine also revoke privileges for all users on the stored routine and errors about missing grants are converted into warnings. Before Bug 33464 such errors could be incorrectly returned to the user, which would later trigger a assertion due to multiple errors being set. mysql-test/suite/funcs_1/r/innodb_storedproc_06.result: Update test case result, grants were already dropped. mysql-test/suite/funcs_1/r/memory_storedproc_06.result: Update test case result, grants were already dropped. mysql-test/suite/funcs_1/r/myisam_storedproc_06.result: Update test case result, grants were already dropped. mysql-test/suite/funcs_1/r/ndb_storedproc_06.result: Update test case result, grants were already dropped. mysql-test/suite/funcs_1/storedproc/storedproc_06.inc: Add comment regarding bug revealed by test case. mysql-test/suite/funcs_1/t/disabled.def: Re-enable test cases, bug has been fixed.
-
unknown authored
into adventure.(none):/home/thek/Development/cpp/mysql-5.1-bugteam
-
unknown authored
mysql-test/r/query_cache_wlock_invalidate_func.result: Adjusted test. Query cache doesn't support multiple statements and thus using a delimiter change won't work. mysql-test/t/disabled.def: Enabled the query_cache_wlock_invalidate_func test. mysql-test/t/query_cache_wlock_invalidate_func.test: Adjusted test. Query cache doesn't support multiple statements and thus using a delimiter change won't work.
-
unknown authored
into a non-const string pointer. client/mysqltest.c: Don't use a constant string as val may be modified later.
-
unknown authored
into mysql.com:/Users/davi/mysql/mysql-5.1-bugteam
-
unknown authored
into noir.wlan.koehntopp.de:/misc/mysql/mysql-5.1-bugteam mysys/my_static.c: Auto merged mysys/my_static.h: Auto merged
-
unknown authored
-
unknown authored
We could allocate chunks larger than 4GB, but did our size-accounting in 32-bit values. This could lead to spurious warnings, inaccurate accounting, and, in theory, data loss. Affected: 64-bit platforms. Debug-build (with safemalloc). At least one buffer larger than 4GB. For potential data loss, a re-alloc on such a buffer would be necessary. mysys/my_static.c: Make memory-accounting 64-bit safe. mysys/my_static.h: Make memory-accounting 64-bit safe. Move in struct for better alignment when 64-bit.
-
- 05 May, 2008 5 commits
-
-
unknown authored
into mysql.com:/Users/davi/mysql/mysql-5.1-bugteam client/mysqltest.c: Auto merged
-
unknown authored
Bug#31237 Test "ndb_views" fails because of differing order of select results mysql-test/suite/funcs_1/r/innodb_views.result: Updated results mysql-test/suite/funcs_1/r/memory_views.result: Updated results mysql-test/suite/funcs_1/r/myisam_views.result: Updated results mysql-test/suite/funcs_1/r/ndb_views.result: Updated results mysql-test/suite/funcs_1/views/views_master.inc: Mangle the row numbers
-
unknown authored
into magare.gmz:/home/kgeorge/mysql/work/merge-5.1-bugteam client/mysqltest.c: Auto merged mysql-test/mysql-test-run.pl: Auto merged
-
unknown authored
into magare.gmz:/home/kgeorge/mysql/work/merge-5.0-bugteam mysql-test/mysql-test-run.pl: Auto merged
-
unknown authored
into mysql1000.dsl.inet.fi:/home/andrei/MySQL/BARE/mysql-5.1-bugteam
-
- 02 May, 2008 8 commits
-
-
unknown authored
The problem is a hack in mysqltest.c::append_field that modifies the exponential notation of floating point numbers by removing a zero after the the symbol 'e' (eg: 00001.2e+018 is converted to 00001.2e+18) but does not take into account the zerofill affect in the start of the string. The solution is to check if the field was zero filled and insert a zero at the start of the string if a zero after the exponential notation symbol is removed. client/mysqltest.c: Preserve zerofill affect when removing a zero after the exponential notation symbol.
-
unknown authored
-
unknown authored
into pilot.mysql.com:/data/msvensson/mysql/mysql-5.1-bugteam client/mysqltest.c: Auto merged dbug/dbug.c: Auto merged mysql-test/mysql-test-run.pl: Auto merged client/mysql_upgrade.c: SCCS merged
-
unknown authored
into pilot.mysql.com:/data/msvensson/mysql/mysql-5.0-bugteam client/mysqltest.c: Auto merged
-
unknown authored
client/mysql_upgrade.c: Add --tmpdir option to mysql_upgrade and use it when creating temporary files. mysql-test/mysql-test-run.pl: Pass --tmpdir to mysql_upgrade
-
unknown authored
- Code in DbugParse was reading from beyond end of the control string dbug/dbug.c: Don't try to parse control strings that hasn't got any tokens or is zero size
-
unknown authored
client/mysqltest.c: Use the --tmpdir location to create temporary files
-
unknown authored
mysql-test/mysql-test-run.pl: Use the requested tmpdir in 'collect_mysqld_features', create it if it does not already exists
-
- 01 May, 2008 3 commits
-
-
unknown authored
into pcrews-mac-local.local:/Users/pcrews/usr/local/bin/data0/build_work/mysql-5.1-trigs
-
unknown authored
into pcrews-mac-local.local:/Users/pcrews/usr/local/bin/data0/build_work/mysql-5.0-trigs
-
unknown authored
into pcrews-mac-local.local:/Users/pcrews/usr/local/bin/data0/build_work/mysql-5.1-trigs client/mysqltest.c: Auto merged
-