- 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 1 commit
-
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/home/hf/work/mrg/my41-mrg
-
- 29 Nov, 2007 1 commit
-
-
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 1 commit
-
-
holyfoot/hf@mysql.com/hfmain.(none) authored
comment fixed as we truly need const_item to be 1 to mark constant function
-
- 24 Nov, 2007 1 commit
-
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/home/hf/work/30284/my41-30284
-
- 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
-
- 14 Nov, 2007 1 commit
-
-
gluh@mysql.com/eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/4.1-opt
-
- 13 Nov, 2007 2 commits
-
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/home/hf/work/31305/my41-31305
-
holyfoot/hf@mysql.com/hfmain.(none) authored
max_length parameter for BLOB-returning functions must be big enough for any possible content. Otherwise the field created for a table will be too small.
-
- 12 Nov, 2007 4 commits
-
-
svoj@mysql.com/june.mysql.com authored
Use proper variable for test.
-
svoj@mysql.com/june.mysql.com authored
-
svoj@mysql.com/june.mysql.com authored
into mysql.com:/home/svoj/devel/mysql/BUG32111/mysql-4.1-engines
-
holyfoot/hf@mysql.com/hfmain.(none) authored
When we insert a record into MYISAM table which is almost 'full', we first write record data in the free space inside a file, and then check if we have enough space after the end of the file. So if we don't have the space, table will left corrupted. Similar error also happens when we updata MYISAM tables. Fixed by modifying write_dynamic_record and update_dynamic_record functions to check for free space before writing parts of a record
-
- 10 Nov, 2007 1 commit
-
-
holyfoot/hf@mysql.com/hfmain.(none) authored
in mysql_creata_like_table() we 'downcase' the complete path to the .frm file. It works fine in standalone case as there usually we only have './' as a path to the datahome, but doesn't work in the embedded server where we add the real path there, so if a directory has uppercase letters in it's name, it won't be found. Fixed by 'downcasing' only database/table pair.
-
- 08 Nov, 2007 1 commit
-
-
kaa@polly.(none) authored
into polly.(none):/home/kaa/src/opt/mysql-4.1-opt
-
- 07 Nov, 2007 1 commit
-
-
kaa@polly.(none) authored
variable in where clause. Problem: the new_item() method of Item_uint used an incorrect constructor. "new Item_uint(name, max_length)" calls Item_uint::Item_uint(const char *str_arg, uint length) which assumes the first argument to be the string representation of the value, not the item's name. This could result in either a server crash or incorrect results depending on usage scenarios. Fixed by using the correct constructor in new_item(): Item_uint::Item_uint(const char *str_arg, longlong i, uint length).
-
- 06 Nov, 2007 1 commit
-
-
svoj@mysql.com/june.mysql.com authored
RENAME TABLE against a table with DATA/INDEX DIRECTORY overwrites the file to which the symlink points. This is security issue, because it is possible to create a table with some name in some non-system database and set DATA/INDEX DIRECTORY to mysql system database. Renaming this table to one of mysql system tables (e.g. user, host) would overwrite the system table. Return an error when the file to which the symlink points exist.
-
- 02 Nov, 2007 3 commits
-
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-4.1-axmrg
-
istruewing@stella.local authored
Preliminarily disabled test case
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-4.1-axmrg
-
- 30 Oct, 2007 3 commits
-
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-4.1-axmrg
-
svoj@mysql.com/june.mysql.com authored
Fulltext boolean mode phrase search may crash server on platforms where size of pointer is not equal to size of unsigned integer (in other words some 64-bit platforms). The problem was integer overflow. Affects 4.1 only.
-
holyfoot/hf@mysql.com/hfmain.(none) authored
Item_func_inet_ntoa and Item_func_conv inherit 'maybe_null' flag from an argument, which is wrong. Both can be NULL with notnull arguments, so that's fixed.
-
- 29 Oct, 2007 1 commit
-
-
joerg@trift2. authored
into trift2.:/MySQL/M41/push-4.1
-
- 25 Oct, 2007 1 commit
-
-
df@pippilotta.erinye.com authored
-
- 24 Oct, 2007 2 commits
-
-
svoj@mysql.com/june.mysql.com authored
into mysql.com:/home/svoj/devel/mysql/BUG31159/mysql-4.1-engines
-
svoj@mysql.com/june.mysql.com authored
ucs2 doesn't provide required by fulltext ctype array. Crash happens because fulltext attempts to use unitialized ctype array. Fixed by converting ucs2 fields to compatible utf8 analogue.
-
- 23 Oct, 2007 1 commit
-
-
gluh@mysql.com/eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/4.1-opt
-
- 19 Oct, 2007 1 commit
-
-
into anubis.xiphis.org:/usr/home/antony/work/mysql-4.1-engines.merge
-
- 18 Oct, 2007 2 commits
-
-
tnurnberg@sin.intern.azundris.com authored
into sin.intern.azundris.com:/misc/mysql/31588/41-31588
-
tnurnberg@sin.intern.azundris.com authored
Buffer used when setting variables was not dimensioned to accomodate trailing '\0'. An overflow by one character was therefore possible. CS corrects limits to prevent such overflows.
-
- 17 Oct, 2007 1 commit
-
-
kaa@polly.(none) authored
-
- 16 Oct, 2007 1 commit
-
-
kaa@polly.(none) authored
into polly.(none):/home/kaa/src/maint/mysql-4.1-maint
-
- 11 Oct, 2007 1 commit
-
-
kaa@polly.(none) authored
myisam_sort_buffer_size. An incorrect length of the sort buffer was used when calculating the maximum number of keys. When myisam_sort_buffer_size is small enough, this could result in the number of keys < number of BUFFPEK structures which in turn led to use of uninitialized BUFFPEKs. Fixed by correcting the buffer length calculation.
-
- 10 Oct, 2007 2 commits
-
-
kaa@polly.(none) authored
into polly.(none):/home/kaa/src/maint/mysql-4.1-maint
-
gluh@mysql.com/eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/4.1-opt
-