- 16 May, 2007 1 commit
-
-
svoj@mysql.com/april.(none) authored
tables In case system doesn't have native pread/pwrite calls (e.g. Windows) and there is CHECK TABLE runs concurrently with another statement that reads from a table, the table may be reported as crashed. This is fixed by locking file descriptor when my_seek is executed on MyISAM index file and emulated pread/pwrite may be executed concurrently. Affects MyISAM tables on platforms that do not have native pread/pwrite calls (e.g. Windows). No deterministic test case for this bug.
-
- 28 Apr, 2007 1 commit
-
-
svoj@mysql.com/june.mysql.com authored
on a BLACKHOLE table Using INSERT DELAYED on BLACKHOLE tables could lead to server crash. This happens because delayed thread wants to upgrade a lock, but BLACKHOLE tables do not have locks at all. This patch rejects attempts to use INSERT DELAYED on MERGE tables.
-
- 26 Apr, 2007 2 commits
-
-
svoj@mysql.com/april.(none) authored
into mysql.com:/home/svoj/devel/mysql/merge/mysql-4.1-engines
-
joerg@trift-lap.fambruehe authored
into trift-lap.fambruehe:/MySQL/M41/push-4.1
-
- 24 Apr, 2007 2 commits
-
-
into mysql.com:/home/ram/work/b27515/b27515.4.1
-
into mysql.com:/home/ram/work/b27515/b27515.4.1
-
- 23 Apr, 2007 2 commits
-
-
tsmith@quadxeon.mysql.com authored
into quadxeon.mysql.com:/benchmarks/ext3/TOSAVE/tsmith/bk/maint/41
-
joerg@debian.(none) authored
into debian.(none):/M41/push-4.1
-
- 20 Apr, 2007 1 commit
-
-
gshchepa/uchum@gshchepa.loc authored
Support for NULL components was incomplete for row comparison, fixed. Added support for abort_on_null at compare_row() like in 5.x
-
- 19 Apr, 2007 1 commit
-
-
svoj@mysql.com/june.mysql.com authored
-
- 18 Apr, 2007 1 commit
-
-
svoj@mysql.com/june.mysql.com authored
into mysql.com:/home/svoj/devel/mysql/BUG24342/mysql-4.1-engines
-
- 17 Apr, 2007 3 commits
-
-
tsmith@siva.hindu.god authored
into siva.hindu.god:/home/tsmith/m/bk/maint/41
-
joerg@trift2. authored
into trift2.:/MySQL/M41/push-4.1
-
Added missed DROP privilege check on the original table for RENAME TABLE command.
-
- 14 Apr, 2007 1 commit
-
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/d2/hf/mrg/mysql-4.1-opt
-
- 12 Apr, 2007 2 commits
-
-
svoj@mysql.com/april.(none) authored
IGNORE/USE/FORCE INDEX hints were honored when choosing FULLTEXT index. With this fix these hints are ignored. For regular indexes we may perform table scan instead of index lookup when IGNORE INDEX was specified. We cannot do this for FULLTEXT in NLQ mode.
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-4.1-opt
-
- 11 Apr, 2007 4 commits
-
-
igor@olga.mysql.com authored
are used as arguments of the IN predicate. Added a function to check compatibility of row expressions. Made sure that this function to be called for Item_func_in objects by fix_length_and_dec().
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-4.1-ndb
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-4.1-ndb
-
jonas@perch.ndb.mysql.com authored
fix commit trigger on multi-update
-
- 10 Apr, 2007 9 commits
-
-
kent@mysql.com/kent-amd64.(none) authored
into mysql.com:/home/kent/bk/tmp3/mysql-4.1-build
-
svoj@mysql.com/april.(none) authored
MERGE engine may return incorrect values when several representations of equal keys are present in the index. For example "groß" and "gross" or "gross" and "gross " (trailing space), which are considered equal, but have different lengths. The problem was that key length was not recalculated after key lookup. Only MERGE engine is affected.
-
msvensson@pilot.blaudden authored
-
msvensson@pilot.blaudden authored
-
msvensson@pilot.blaudden authored
-
msvensson@pilot.blaudden authored
-
msvensson@pilot.blaudden authored
into pilot.blaudden:/home/msvensson/mysql/mysql-4.1-maint
-
msvensson@pilot.blaudden authored
-
msvensson@pilot.blaudden authored
into pilot.blaudden:/home/msvensson/mysql/mysql-4.1-maint
-
- 07 Apr, 2007 2 commits
-
-
joerg@trift2. authored
into trift2.:/MySQL/M41/push-4.1
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/d2/hf/mrg/mysql-4.1-opt
-
- 05 Apr, 2007 3 commits
-
-
msvensson@shellback.(none) authored
Usage: query_sorted <query>;
-
msvensson@pilot.blaudden authored
Cleanup exit handling
-
kent@mysql.com/kent-amd64.(none) authored
configure.in.rej include/my_global.h.rej BUILD/SETUP.sh.rej mysys/thr_alarm.c.rej include/my_pthread.h.rej
-
- 04 Apr, 2007 4 commits
-
-
msvensson@pilot.blaudden authored
- length($sockdir) >= 80 !!
-
msvensson@pilot.blaudden authored
error code indicating test should be skipped
-
msvensson@pilot.blaudden authored
"if with query" and "while with query"
-
igor@olga.mysql.com authored
-
- 03 Apr, 2007 1 commit
-
-
igor@olga.mysql.com authored
IN/BETWEEN predicates in sorting expressions. Wrong results may occur when the select list contains an expression with IN/BETWEEN predicate that differs from a sorting expression by an additional NOT only. Added the method Item_func_opt_neg::eq to compare correctly expressions containing [NOT] IN/BETWEEN. The eq method inherited from the Item_func returns TRUE when comparing 'a IN (1,2)' with 'a NOT IN (1,2)' that is not, of course, correct.
-