- 12 Mar, 2008 1 commit
-
-
kaa@kaamos.(none) authored
into kaamos.(none):/data/src/opt/mysql-4.1-opt
-
- 29 Feb, 2008 2 commits
-
-
gluh@mysql.com/eagle.(none) authored
-
gluh@mysql.com/eagle.(none) authored
added new function test_if_data_home_dir() which checks that path does not contain mysql data home directory. Using of mysql data home directory in DATA DIRECTORY & INDEX DIRECTORY is disallowed.
-
- 17 Feb, 2008 1 commit
-
-
kaa@kaamos.(none) authored
into kaamos.(none):/data/src/opt/mysql-4.1-opt
-
- 10 Feb, 2008 1 commit
-
-
Field data for a query was stored to the stmt->alloc that is emptied with mysql_stmt_close statement only. That means a lot of memory can be occupied without a reason if used doesn't call mysql_stmt_close often.
-
- 29 Jan, 2008 1 commit
-
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-4.1-build
-
- 28 Jan, 2008 1 commit
-
-
joerg@trift2. authored
into trift2.:/MySQL/M41/push-4.1
-
- 25 Jan, 2008 1 commit
-
-
cmiller@zippy.cornsilk.net authored
running queries Bug#33976: buffer overflow of variable time_buff in function com_go() An internal buffer was too short. Overextending could smash the stack on some architectures and cause SEGVs. This is not a problem that could be exploited to run arbitrary code. To fix, I expanded one buffer to cover all the size that could be written to (we know the abolute max).
-
- 22 Jan, 2008 1 commit
-
-
tsmith@ramayana.hindu.god authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/41
-
- 21 Jan, 2008 1 commit
-
-
joerg@trift2. authored
into trift2.:/MySQL/M41/push-4.1
-
- 27 Dec, 2007 1 commit
-
-
joerg@trift2. authored
Fix the code to get the "libgcc" file name so that the failure of Intel's ICC to provide this information does not cause any problems. This fixes bug#33536 Option "--print-libgcc-file" does not work with ICC compiler
-
- 17 Dec, 2007 3 commits
-
-
into mysql.com:/misc/mysql/31752_/41-31752_
-
fix test program
-
into mysql.com:/misc/mysql/31752_/41-31752_
-
- 13 Dec, 2007 1 commit
-
-
gluh@mysql.com/eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/4.1-opt
-
- 10 Dec, 2007 2 commits
-
-
tsmith@ramayana.hindu.god authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/41
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-4.1-build
-
- 06 Dec, 2007 2 commits
-
-
tsmith@ramayana.hindu.god authored
-
post-fixes: prevent semi-related overflow, additional comments
-
- 05 Dec, 2007 1 commit
-
-
tsmith@ramayana.hindu.god authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/41
-
- 01 Dec, 2007 2 commits
-
-
into mysql.com:/misc/mysql/32707/41-32707
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/home/hf/work/mrg/my41-mrg
-
- 30 Nov, 2007 5 commits
-
-
mleich@four.local.lan authored
into four.local.lan:/work/trees/mysql-4.1-build-src-clean
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/home/hf/work/mrg/my41-mrg
-
mleich@four.local.lan authored
Bug#31030 rpl000015.test fails if $MYSQL_TCP_PORT != 3306 Note: This bug does not occur in MySQL 5.0 and up, because ChangeSet 1.2328.2.1 2006/11/27 for MySQL 5.0 prevents this. The 5.0 fix uses the environment variable DEFAULT_MASTER_PORT which is set by mysql-test-run.pl. mysql-test-run.pl in 4.1 does not set this variable. There are two alternatives: 1) Backport the 5.0 fix for this test including modifications to mysql-test-run.pl and mysql-test-run-shell. This is a not acceptable impact on an old MySQL version. 2) Fix the problem different than in 5.0 like in the current ChangeSet + do not apply these changes when upmerging to 5.0
-
kent@mysql.com/kent-amd64.(none) authored
Added 64 bit Mac OS X hard coded settings, for universal binaries
-
kent@mysql.com/kent-amd64.(none) authored
-
- 29 Nov, 2007 2 commits
-
-
kent@mysql.com/kent-amd64.(none) authored
Added 64 bit Mac OS X hard coded settings, for universal binaries
-
holyfoot/hf@mysql.com/hfmain.(none) authored
Denormalized DOUBLE-s can't be properly handled by old MIPS processors. So we need to enable specific mode for them so IRIX will do use software round to handle such numbers.
-
- 27 Nov, 2007 1 commit
-
-
Miscalculation in protocol-layer: size buffer correctly so even really long error messages cannot overflow our buffer.
-
- 26 Nov, 2007 2 commits
-
-
holyfoot/hf@mysql.com/hfmain.(none) authored
comment fixed as we truly need const_item to be 1 to mark constant function
-
strmake() calls are easy to get wrong. Add checks in extra debug mode to identify possible exploits. Remove some dead code. Remove some off-by-one errors identified with new checks.
-
- 24 Nov, 2007 1 commit
-
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/home/hf/work/30284/my41-30284
-
- 21 Nov, 2007 1 commit
-
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-4.1-axmrg
-
- 20 Nov, 2007 1 commit
-
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/home/hf/work/31868/my41-31868
-
- 19 Nov, 2007 1 commit
-
-
holyfoot/hf@mysql.com/hfmain.(none) authored
SPATIAL key is fine actually, but the chk_key() function mistakenly returns error. It tries to compare checksums of btree and SPATIAL keys while the checksum for the SPATIAL isn't calculated (always 0). Same thing with FULLTEXT keys is handled using full_text_keys counter, so fixed by counting both SPATIAL and FULLTEXT keys in that counter.
-
- 17 Nov, 2007 1 commit
-
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/home/hf/work/31158/my41-31158
-
- 16 Nov, 2007 2 commits
-
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-4.1-axmrg
-
joerg@trift2. authored
into trift2.:/MySQL/M41/push-4.1
-
- 14 Nov, 2007 1 commit
-
-
joerg@trift2. authored
into trift2.:/MySQL/M41/push-4.1
-