- 30 Sep, 2006 1 commit
-
-
dlenev@mockturtle.local authored
-
- 29 Sep, 2006 8 commits
-
-
dlenev@mockturtle.local authored
into mockturtle.local:/home/dlenev/src/mysql-5.1-bg20670
-
dlenev@mockturtle.local authored
-
dlenev@mockturtle.local authored
into mockturtle.local:/home/dlenev/src/mysql-5.1-rt-merge
-
dlenev@mockturtle.local authored
into mockturtle.local:/home/dlenev/src/mysql-5.1-bg20670
-
dlenev@mockturtle.local authored
into mockturtle.local:/home/dlenev/src/mysql-5.1-rt-merge
-
dlenev@mockturtle.local authored
into mockturtle.local:/home/dlenev/src/mysql-5.0-rt-merge
-
dlenev@mockturtle.local authored
-
dlenev@mockturtle.local authored
into mockturtle.local:/home/dlenev/src/mysql-5.0-rt-merge
-
- 28 Sep, 2006 10 commits
-
-
dlenev@mockturtle.local authored
create_tmp_table()". The fix for bug 21787 "COUNT(*) + ORDER BY + LIMIT returns wrong result" introduced valgrind warnings which occured during execution of information_schema.test and sp-prelocking.test in version 5.0. There were no user visible effects. The latter fix made create_tmp_table() dependant on THD::lex::current_select value. Valgrind warnings occured when this function was executed and THD::lex::current_select member pointed to uninitialized SELECT_LEX instance. This fix tries to remove this dependancy by moving some logic outside of create_tmp_table() function.
-
gluh@gluh.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.1
-
gluh@mysql.com/gluh.(none) authored
-
anozdrin/alik@alik. authored
into alik.:/mnt/raid/alik/MySQL/devel/5.1-rt-merged
-
anozdrin/alik@alik. authored
-
anozdrin/alik@alik. authored
into alik.:/mnt/raid/alik/MySQL/devel/5.1-rt-merged
-
gluh@gluh.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.1
-
andrey@example.com authored
into example.com:/work/mysql-5.1-runtime-fresh2
-
dlenev@mockturtle.local authored
into mockturtle.local:/home/dlenev/src/mysql-4.1-runtime
-
petr/cps@owlet.local authored
into mysql.com:/home/cps/mysql/trees/5.1-runtime-new
-
- 27 Sep, 2006 11 commits
-
-
andrey@example.com authored
into example.com:/work/mysql-5.0-runtime
-
andrey@example.com authored
-
andrey@example.com authored
into example.com:/work/mysql-5.1-runtime-fresh2
-
andrey@example.com authored
There was possible stack overrun in an edge case which handles invalid body of a SP in mysql.proc . That should be case when mysql.proc has been changed manually. Though, due to bug 21513, it can be exploited without having access to mysql.proc only being able to create a stored routine.
-
gluh@mysql.com/gluh.(none) authored
-
gluh@mysql.com/gluh.(none) authored
-
petr/cps@mysql.com/owlet.local authored
at the moment, so we can safely do that). Update an error mesage to make it translateable.
-
gluh@mysql.com/gluh.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.0
-
gluh@mysql.com/gluh.(none) authored
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.1-bug21414
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-bug21414
-
- 26 Sep, 2006 5 commits
-
-
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1-runtime
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0-runtime
-
A better fix for bug#10025. Fixed test case plus added new tests. After fixing Bug#20208 "Blobs greater than 8K are being truncated to 8K" the fix to bug#10025 "Misleading error with COLLATE mediumtext and UNION" became more accurate. Earlier mediumtext got converted to longtext, although mediumtext was enough to contain the results. Now it converts correctly to mediumtext, if the length does not exceed that and if none of the original fields were type longtext. Type longtext still converts correctly to type longtext, as the extra tests prove.
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
- 25 Sep, 2006 5 commits
-
-
andrey@example.com authored
when set to DISABLED It was a silly ordering number error.
-
andrey@example.com authored
ALTER EVENT in stored procedure body led to a crash during the procedure call. Affected was only ALTER EVENT which changed the interval of the event. No problems with AT, STARTS, ENDS and so on.
-
andrey@example.com authored
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/bug22379_runtime/my51-bug22379_runtime
-
-