- 07 Feb, 2008 1 commit
-
-
msvensson@pilot.mysql.com authored
-
- 23 Oct, 2007 1 commit
-
-
msvensson@pilot.mysql.com authored
-
- 15 Oct, 2007 4 commits
-
-
msvensson@pilot.mysql.com authored
into pilot.mysql.com:/data/msvensson/mysql/mysql-5.0-maint
-
ramil/ram@ramil.myoffice.izhnet.ru authored
into mysql.com:/home/ram/work/b31154/b31154.5.0
-
ramil/ram@ramil.myoffice.izhnet.ru authored
into mysql.com:/home/ram/work/b31154/b31154.5.0
-
ramil/ram@ramil.myoffice.izhnet.ru authored
into mysql.com:/home/ram/work/b30885/b30885.5.0
-
- 12 Oct, 2007 10 commits
-
-
mtaylor@solace.(none) authored
into solace.(none):/home/mtaylor/src/mysql/mysql-5.0-maint
-
mtaylor@solace.(none) authored
-
tnurnberg@sin.intern.azundris.com authored
into sin.intern.azundris.com:/home/tnurnberg/30951/50-30951
-
kaa@polly.(none) authored
into polly.(none):/home/kaa/src/maint/mysql-5.0-maint
-
kaa@polly.(none) authored
(compiler issue ?) Problem: Improper compile-time flags on AIX prevented use of files > 2 GB. This resulted in Max_data_length being truncated to 2 GB by MyISAM code. Solution: Reverted large-file changes from the fix for bug10776. We need to define _LARGE_FILES on AIX to have support for files > 2 GB. Since _LARGE_FILE_API is incompatible with _LARGE_FILES and may be automatically defined by including standards.h, we also need a workaround to avoid this conflict.
-
tnurnberg@sin.intern.azundris.com authored
into sin.intern.azundris.com:/home/tnurnberg/30951/50-30951
-
tnurnberg@sin.intern.azundris.com authored
makedate() will fold years below 100 into the 1970-2069 range. CS removes code that also wrongly folded years between 100 and 200 into that range, which should be left unchanged. Backport from 5.1.
-
tnurnberg@sin.intern.azundris.com authored
into sin.intern.azundris.com:/home/tnurnberg/30821/50-30821
-
tnurnberg@sin.intern.azundris.com authored
Options to mysqld were not processed correctly because switch statement was missing some "break"s. CS adds them. No test case; would require .opt file and server restart. Manually tested.
-
mtaylor@solace.(none) authored
-
- 11 Oct, 2007 2 commits
-
-
Problem: GROUP_CONCAT(DISTINCT BIT_FIELD...) uses a tree to store keys; which are constructed using a temporary table fields, see Item_func_group_concat::setup(). As a) we don't store null bits in the tree where the bit fields store parts of their data and b) there's no method to properly compare two table records we've got problem. Fix: convert BIT fields to INT in the temporary table used.
-
ssh://bk-internal.mysql.com//home/bk/mysql-5.0-maintkaa@polly.(none) authored
into polly.(none):/home/kaa/src/maint/mysql-5.0-maint
-
- 10 Oct, 2007 6 commits
-
-
tsmith@ramayana.hindu.god authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/50
-
tsmith@ramayana.hindu.god authored
Introduced in mark_transaction_to_rollback(), part of fix for bug 24989; fix is to check thd for NULL before using it.
-
kaa@polly.(none) authored
into polly.(none):/home/kaa/src/maint/mysql-5.0-maint
-
kaa@polly.(none) authored
into polly.(none):/home/kaa/src/maint/mysql-5.0-maint
-
kaa@polly.(none) authored
into polly.(none):/home/kaa/src/maint/mysql-4.1-maint
-
kaa@polly.(none) authored
into polly.(none):/home/kaa/src/maint/bug28878/my50-bug28878
-
- 09 Oct, 2007 8 commits
-
-
tsmith@ramayana.hindu.god authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/50
-
tsmith@ramayana.hindu.god authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/50
-
as PS protocol gives slightly different metadata.
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.0-maint
-
ramil/ram@ramil.myoffice.izhnet.ru authored
into mysql.com:/home/ram/work/b31249/b31249.5.0
-
bitmap_is_set(table->write_set, fiel Problem: creating a temporary table we allocate the group buffer if needed followed by table bitmaps (see create_tmp_table()). Reserving less memory for the group buffer than actually needed (used) for values retrieval may lead to overlapping with followed bitmaps in the memory pool that in turn leads to unpredictable consequences. As we use Item->max_length sometimes to calculate group buffer size, it must be set to proper value. In this particular case Item_datetime_typecast::max_length is too small. Another problem is that we use max_length to calculate the group buffer key length for items represented as DATE/TIME fields which is superfluous. Fix: set Item_datetime_typecast::max_length properly, accurately calculate the group buffer key length for items represented as DATE/TIME fields in the buffer.
-
iggy@alf.(none) authored
into alf.(none):/src/bug28774/my50-bug28774
-
iggy@alf.(none) authored
doesn't clean them up - Make sure to cleanup temporary files after use.
-
- 06 Oct, 2007 1 commit
-
-
tnurnberg@sin.intern.azundris.com authored
into sin.intern.azundris.com:/home/tnurnberg/31253/50-31253
-
- 05 Oct, 2007 7 commits
-
-
tnurnberg@sin.intern.azundris.com authored
into sin.intern.azundris.com:/home/tnurnberg/19828/50-19828
-
msvensson@pilot.mysql.com authored
into pilot.mysql.com:/data/msvensson/mysql/mysql-5.0-maint
-
msvensson@pilot.mysql.com authored
-
msvensson@pilot.mysql.com authored
into pilot.mysql.com:/data/msvensson/mysql/mysql-5.0-maint
-
msvensson@shellback.(none) authored
-
msvensson@shellback.(none) authored
-
cmiller@zippy.cornsilk.net authored
Our web server has been restructured several times, and references to it in our source code has stayed the same. This patch from Paul DuBois updates all URLs to modern semantics.
-