- 09 May, 2008 4 commits
-
-
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 4 commits
-
-
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 6 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)
-
davi@mysql.com/endora.local authored
has been fixed and closed.
-
- 06 May, 2008 10 commits
-
-
davi@endora.local authored
into mysql.com:/Users/davi/mysql/mysql-5.1-bugteam
-
davi@endora.local authored
into mysql.com:/Users/davi/mysql/mysql-5.1-bugteam
-
davi@mysql.com/endora.local 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.
-
thek@adventure.(none) authored
into adventure.(none):/home/thek/Development/cpp/mysql-5.1-bugteam
-
thek@adventure.(none) authored
-
davi@mysql.com/endora.local authored
into a non-const string pointer.
-
davi@endora.local authored
into mysql.com:/Users/davi/mysql/mysql-5.1-bugteam
-
tnurnberg@noir.wlan.koehntopp.de authored
into noir.wlan.koehntopp.de:/misc/mysql/mysql-5.1-bugteam
-
gkodinov/kgeorge@magare.gmz authored
-
tnurnberg@noir.wlan.koehntopp.de 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.
-
- 05 May, 2008 5 commits
-
-
davi@endora.local authored
into mysql.com:/Users/davi/mysql/mysql-5.1-bugteam
-
mleich@five.local.lan authored
Bug#31237 Test "ndb_views" fails because of differing order of select results
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/work/merge-5.1-bugteam
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/work/merge-5.0-bugteam
-
aelkin/andrei@mysql1000.dsl.inet.fi authored
into mysql1000.dsl.inet.fi:/home/andrei/MySQL/BARE/mysql-5.1-bugteam
-
- 02 May, 2008 8 commits
-
-
davi@mysql.com/endora.local 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.
-
msvensson@pilot.mysql.com authored
-
msvensson@pilot.mysql.com authored
into pilot.mysql.com:/data/msvensson/mysql/mysql-5.1-bugteam
-
msvensson@pilot.mysql.com authored
into pilot.mysql.com:/data/msvensson/mysql/mysql-5.0-bugteam
-
msvensson@pilot.mysql.com authored
-
msvensson@pilot.mysql.com authored
- Code in DbugParse was reading from beyond end of the control string
-
msvensson@pilot.mysql.com authored
-
msvensson@pilot.mysql.com authored
-
- 01 May, 2008 3 commits
-
-
pcrews@pcrews-mac-local.local authored
into pcrews-mac-local.local:/Users/pcrews/usr/local/bin/data0/build_work/mysql-5.1-trigs
-
pcrews@pcrews-mac-local.local authored
into pcrews-mac-local.local:/Users/pcrews/usr/local/bin/data0/build_work/mysql-5.0-trigs
-
pcrews@pcrews-mac-local.local authored
into pcrews-mac-local.local:/Users/pcrews/usr/local/bin/data0/build_work/mysql-5.1-trigs
-