- 11 Oct, 2006 1 commit
-
-
kaa@polly.local authored
into polly.local:/tmp/maint/bug11655/my50-bug11655
-
- 04 Oct, 2006 1 commit
-
-
kaa@polly.local authored
- bug #11655 "Wrong time is returning from nested selects - maximum time exists - input and output TIME values were not validated properly in several conversion functions - bug #20927 "sec_to_time treats big unsigned as signed" - integer overflows were not checked in several functions. As a result, input values like 2^32 or 3600*2^32 were treated as 0 - BIGINT UNSIGNED values were treated as SIGNED in several functions - in cases where both input string truncation and out-of-range TIME value occur, only 'truncated incorrect time value' warning was produced
-
- 19 Sep, 2006 3 commits
-
-
thek@kpdesk.mysql.com authored
into kpdesk.mysql.com:/home/thek/dev2/bug21139/my50-bug21139
-
thek@kpdesk.mysql.com authored
- Access checks are omitted when compliled without --with-embedded-privilege-control - Patch: skip this test
-
msvensson@shellback.(none) authored
- Remove the wildcard dependcy on the charset xml files
-
- 18 Sep, 2006 1 commit
-
-
msvensson@shellback.(none) authored
- Make built sources only depend on it's sources not the built tool
-
- 06 Sep, 2006 4 commits
-
-
tsmith@maint1.mysql.com authored
into maint1.mysql.com:/data/localhome/tsmith/bk/bfx/my50-bfx
-
tsmith@maint1.mysql.com authored
-
tsmith@maint1.mysql.com authored
Fix OPT_MYISAM_STATS_METHOD case, where the NULLS_EQUAL and NULLS_NOT_EQUAL methods were mixed up
-
tsmith@maint1.mysql.com authored
-
- 01 Sep, 2006 1 commit
-
-
cmiller@maint1.mysql.com authored
Provide a more extensible, easier-to-change way of reordering test cases.
-
- 15 Aug, 2006 1 commit
-
-
cmiller@maint1.mysql.com authored
Zero-length variables caused failures when using the length to look up the name in a hash. Instead, signal that no zero-length name can ever be found and that to encounter one is a syntax error.
-
- 01 Aug, 2006 3 commits
-
-
tsmith@maint1.mysql.com authored
Fixes: - bug #19834: Using cursors when running in READ-COMMITTED can cause InnoDB to crash - bug #21112: InnoDB slow with > 100,000 .ibd files - bug #21113: Duplicate printout in SHOW INNODB STATUS
-
into mysql.com:/users/lthalmann/bk/MERGE/mysql-5.0-merge
-
into mysql.com:/users/lthalmann/bk/MERGE/mysql-5.0-merge
-
- 31 Jul, 2006 2 commits
-
-
into mysql.com:/users/lthalmann/bk/MERGE/mysql-5.0-merge
-
into mysql.com:/users/lthalmann/bk/MERGE/mysql-4.1-merge
-
- 29 Jul, 2006 6 commits
-
-
into mysql.com:/Users/kent/mysql/bk/mysql-5.0
-
into mysql.com:/Users/kent/mysql/bk/mysql-4.1
-
Corrected typo
-
kroki/tomash@moonlight.intranet authored
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-merge
-
Converted "udf_example.cc" to C, avoids C++ runtime lib dependency (bug#21336)
-
- 28 Jul, 2006 9 commits
-
-
into mysql.com:/Users/kent/mysql/bk/mysql-4.1
-
Man page for mysqld command move to section 8 (bug#21220)
-
Man page for "mysqld" command move to section 8 (bug#21220)
-
Man page for "mysqld" command move to section 8 (bug#21220)
-
into mysql.com:/Users/kent/mysql/bk/mysql-5.0-new
-
into mysql.com:/Users/kent/mysql/bk/mysql-5.0-new
-
Renamed variable, to avoid name clash with macro "rem_size" on AIX 5.3 and "/usr/include/sys/xmem.h" (bug#17648) asn.cpp, asn.hpp: Avoid name clash with NAME_MAX
-
tsmith@maint1.mysql.com authored
into maint1.mysql.com:/data/localhome/tsmith/bk/global-50
-
-
- 27 Jul, 2006 5 commits
-
-
-
kroki/tomash@moonlight.intranet authored
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-main
-
kroki/tomash@moonlight.intranet authored
Too many cursors (more than 1024) could lead to memory corruption. This affects both, stored routines and C API cursors, and the threshold is per-server, not per-connection. Similarly, the corruption could happen when the server was under heavy load (executing more than 1024 simultaneous complex queries), and this is the reason why this bug is fixed in 4.1, which doesn't support cursors. The corruption was caused by a bug in the temporary tables code, when an attempt to create a table could lead to a write beyond allocated space. Note, that only internal tables were affected (the tables created internally by the server to resolve the query), not tables created with CREATE TEMPORARY TABLE. Another pre-condition for the bug is TRUE value of --temp-pool startup option, which, however, is a default. The cause of a bug was that random memory was overwritten in bitmap_set_next() due to out-of-bound memory access.
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-main
-
- 26 Jul, 2006 3 commits
-
-
tsmith/tim@siva.hindu.god authored
into siva.hindu.god:/usr/home/tim/m/bk/global-50
-
kroki/tomash@moonlight.intranet authored
Too many cursors (more than 1024) could lead to memory corruption. This affects both, stored routines and C API cursors, and the threshold is per-server, not per-connection. Similarly, the corruption could happen when the server was under heavy load (executing more than 1024 simultaneous complex queries), and this is the reason why this bug is fixed in 4.1, which doesn't support cursors. The corruption was caused by a bug in the temporary tables code, when an attempt to create a table could lead to a write beyond allocated space. Note, that only internal tables were affected (the tables created internally by the server to resolve the query), not tables created with CREATE TEMPORARY TABLE. Another pre-condition for the bug is TRUE value of --temp-pool startup option, which, however, is a default. The cause of a bug was that random memory was overwritten in bitmap_set_next() due to out-of-bound memory access.
-
aivanov@mysql.com authored
-