- 18 May, 2007 2 commits
-
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-4.1-ndb
-
jonas@perch.ndb.mysql.com authored
Make sure that data can not e left lingering in receive buffer
-
- 10 May, 2007 1 commit
-
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-4.1-ndb
-
- 08 May, 2007 1 commit
-
-
gni/root@dev3-221.dev.cn.tlan authored
into dev3-221.dev.cn.tlan:/home/ngb/mysql/mysql-4.1/mysql-4.1-ndb
-
- 07 May, 2007 1 commit
-
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/d2/hf/mrg/mysql-4.1-opt
-
- 04 May, 2007 1 commit
-
-
gkodinov/kgeorge@magare.gmz authored
When checking for applicability of join cache we must disable its usage only if there is no temp table in use. When a temp table is used we can use join cache (and it will not make the result-set unordered) to fill the temp table. The filesort() operation is then applied to the data in the temp table and hence is not affected by join cache usage. Fixed by narrowing the condition for disabling join cache to exclude the case where temp table is used.
-
- 03 May, 2007 1 commit
-
-
evgen@moonbone.local authored
The generic string to int conversion was used by the Item_func_signed and the Item_func_unsigned classes to convert DATE/DATETIME values to the SIGNED/UNSIGNED type. But this conversion produces wrong results for such values. Now if the item which result has to be converted can return its result as longlong then the item->val_int() method is used to allow the item to carry out the conversion itself and return the correct result. This condition is checked in the Item_func_signed::val_int() and the Item_func_unsigned::val_int() functions.
-
- 02 May, 2007 1 commit
-
-
joerg@trift2. authored
-
- 30 Apr, 2007 1 commit
-
-
igor@olga.mysql.com authored
-
- 29 Apr, 2007 5 commits
-
-
igor@olga.mysql.com authored
some rollup rows (rows with NULLs for grouping attributes) if GROUP BY list contained constant expressions. This happened because the results of constant expressions were not put in the temporary table used for duplicate elimination. In fact a constant item from the GROUP BY list of a ROLLUP query can be replaced for an Item_null_result object when a rollup row is produced . Now the JOIN::rollup_init function wraps any constant item referenced in the GROYP BY list of a ROLLUP query into an Item_func object of a special class that is never detected as constant item. This ensures creation of fields for such constant items in temporary tables and guarantees right results when the result of the rollup operation first has to be written into a temporary table, e.g. in the cases when duplicate elimination is required.
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/d2/hf/mrg/mysql-4.1-opt
-
gshchepa/uchum@gshchepa.loc authored
-
gshchepa/uchum@gshchepa.loc authored
into gshchepa.loc:/home/uchum/work/bk-trees/mysql-4.1-opt-13191
-
gshchepa/uchum@gshchepa.loc authored
-
- 28 Apr, 2007 2 commits
-
-
gshchepa/uchum@gshchepa.loc authored
INSERT...ON DUPLICATE KEY UPDATE may cause error 1032: "Can't find record in ..." if we are inserting into InnoDB table unique index of partial key with underlying UTF-8 string field. This error occurs because INSERT...ON DUPLICATE uses a wrong procedure to copy string fields of multi-byte character sets for index search.
-
gshchepa/uchum@gshchepa.loc authored
This bug occurs when error message length exceeds allowed limit: my_error() function outputs "%s" sequences instead of long string arguments. Formats like %-.64s are very common in errmsg.txt files, however my_error() function simply ignores precision of those formats.
-
- 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 5 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
-