- 13 May, 2008 14 commits
-
-
pcrews@pcrews-mac-local.local authored
Split the test into 3 smaller parts, reducing single test run time. NDB variant still disabled. The runtime for a single test is greater than the runtime for the Innodb variant that was timing out. The test works, but disabled for Build systems.
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/work/win64-warn-5.1-bugteam
-
gshchepa/uchum@host.loc authored
into host.loc:/work/bk/5.1-bugteam
-
gshchepa/uchum@host.loc authored
max_heap_table_size_basic_32, query_cache_size_basic_32 and tmp_table_size_basic_32 tests have been disabled according to bug #36522.
-
gkodinov/kgeorge@magare.gmz authored
subselects into account It is forbidden to use the SELECT INTO construction inside UNION statements unless on the last SELECT of the union. The parser records whether it has seen INTO or not when parsing a UNION statement. But if the INTO was legally used in an outer query, an error is thrown if UNION is seen in a subquery. Fixed in 5.0 by remembering the nesting level of INTO tokens and mitigate the error unless it collides with the UNION.
-
gshchepa/uchum@host.loc authored
Post-push test case update (bug #30059).
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/work/win64-warn-5.1-bugteam
-
gkodinov/kgeorge@magare.gmz authored
-
gshchepa/uchum@host.loc authored
into host.loc:/work/bk/5.1-bugteam
-
gshchepa/uchum@host.loc authored
into host.loc:/work/bk/5.1-bugteam
-
thek@adventure.(none) authored
into adventure.(none):/home/thek/Development/cpp/mysql-5.1-bugteam
-
thek@adventure.(none) authored
Fixed build failure depending on events in embedded build.
-
gshchepa/uchum@host.loc authored
into host.loc:/work/bk/5.1-bugteam
-
gshchepa/uchum@host.loc authored
into host.loc:/work/bk/5.0-bugteam
-
- 12 May, 2008 9 commits
-
-
gshchepa/uchum@host.loc authored
into host.loc:/work/bk/5.1-bugteam
-
gshchepa/uchum@host.loc authored
into host.loc:/work/bk/5.1-bugteam
-
gshchepa/uchum@host.loc authored
into host.loc:/work/bk/5.0-bugteam
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/work/fixes-5.1-bugteam
-
gkodinov/kgeorge@magare.gmz authored
-
gshchepa/uchum@host.loc authored
The REPAIR TABLE ... USE_FRM query silently corrupts data of tables with old .FRM file version. The mysql_upgrade client program or the REPAIR TABLE query (without the USE_FRM clause) can't prevent this trouble, because in the common case they don't upgrade .FRM file to compatible structure. 1. Evaluation of the REPAIR TABLE ... USE_FRM query has been modified to reject such tables with the message: "Failed repairing incompatible .FRM file". 2. REPAIR TABLE query (without USE_FRM clause) evaluation has been modified to upgrade .FRM files to current version. 3. CHECK TABLE ... FOR UPGRADE query evaluation has been modified to return error status when .FRM file has incompatible version. 4. mysql_upgrade and mysqlcheck client programs call CHECK TABLE FOR UPGRADE and REPAIR TABLE queries, so their behaviors have been changed too to upgrade .FRM files with incompatible version numbers.
-
thek@adventure.(none) authored
into adventure.(none):/home/thek/Development/cpp/mysql-5.1-bugteam
-
thek@adventure.(none) authored
SHOW commands fail in embedded mode because schema_table array doesn't correspond to enum_schema_tables. This patch implements a dummy implementation of the abstract fill_table function to be used when the event scheduler (or other core feature) isn't part of the build.
-
gkodinov/kgeorge@magare.gmz authored
- a 64 bit compile warning in embedded - disabled the new (and failing tests for Bug#36522
-
- 10 May, 2008 1 commit
-
-
tsmith@ramayana.hindu.god authored
Addresses the following bugs: Change the fix for Bug#32440 to show bytes instead of kilobytes in INFORMATION_SCHEMA.TABLES.DATA_FREE. branches/5.1: Fix bug#29507 TRUNCATE shows to many rows effected In InnoDB, the row count is only a rough estimate used by SQL optimization. InnoDB is now return row count 0 for TRUNCATE operation. branches/5.1: Fix bug#35537 - Innodb doesn't increment handler_update and handler_delete Add the calls to ha_statistic_increment() in ha_innobase::delete_row() and ha_innobase::update_row(). Fix Bug#36169 create innodb compressed table with too large row size crashed Sometimes it is possible that row_drop_table_for_mysql(index->table_name, trx, FALSE); is invoked in row_create_index_for_mysql() when the index object is freed so copy the table name to a safe place beforehand and use the copy. Fix Bug#36434 ha_innodb.so is installed in the wrong directory Change pkglib_LTLIBRARIES with pkgplugin_LTLIBRARIES which has been forgotten in this commit: http://lists.mysql.com/commits/40206
-
- 09 May, 2008 6 commits
-
-
hhunger@hh-nb.hungers authored
into hh-nb.hungers:/work/merge/mysql-5.1-36522
-
thek@adventure.(none) authored
Enable previously disabled test cases which were tested against the embedded build. The test cases are modified so that they require non-embedded build.
-
thek@adventure.(none) authored
Missing file: include/is_embedded.inc This file was left out of the initial changeset by misstake.
-
thek@adventure.(none) authored
into adventure.(none):/home/thek/Development/cpp/mysql-5.1-bugteam
-
thek@adventure.(none) 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.
-
tsmith@ramayana.hindu.god 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.
-
- 08 May, 2008 5 commits
-
-
hhunger@hh-nb.hungers authored
-
test change for 5.1+ (show create view adds two columns in 5.1) Patch only for 5.1+
-
into client-10-129-10-147.upp.off.mysql.com:/Users/mattiasj/clones/topush-51-bugteam
-
into client-10-129-10-147.upp.off.mysql.com:/Users/mattiasj/clones/topush-50-bugteam
-
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.
-
- 07 May, 2008 5 commits
-
-
davi@endora.local authored
into mysql.com:/Users/davi/mysql/mysql-5.1-bugteam
-
sven@riska.(none) authored
into riska.(none):/home/sven/bkroot/5.1-bugteam
-
sven@riska.(none) 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.
-
sven@riska.(none) 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.
-
sergefp@mysql.com 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)
-