- 25 Sep, 2007 1 commit
-
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.1-build
-
- 24 Sep, 2007 1 commit
-
-
jperkin@production.mysql.com authored
into production.mysql.com:/usersnfs/jperkin/bk/build-5.1
-
- 22 Sep, 2007 1 commit
-
-
jonathan@bagpuss.adsl.perkin.org.uk authored
cmake list are auto-generated and thus still required. Correct fix not yet known.
-
- 21 Sep, 2007 2 commits
-
-
gkodinov/kgeorge@macbook.local authored
-
gkodinov/kgeorge@macbook.local authored
-
- 20 Sep, 2007 6 commits
-
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.1-opt
-
gluh@mysql.com/eagle.(none) authored
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.1-opt
-
gluh@mysql.com/eagle.(none) authored
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.1-opt
-
gluh@mysql.com/eagle.(none) authored
added get_field_default_value() function which obtains default value from the field (used in store_create_info() & get_schema_column_record() functions)
-
- 19 Sep, 2007 5 commits
-
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B30639-5.1-opt
-
gkodinov/kgeorge@magare.gmz authored
The parser uses ulonglong to store the LIMIT number. This number then is stored into a variable of type ha_rows. ha_rows is either 4 or 8 byte depending on the BIG_TABLES define from config.h So an overflow may occur (and LIMIT becomes zero) while storing an ulonglong value in ha_rows. Fixed by : 1. Using the maximum possible value for ha_rows on overflow 2. Defining BIG_TABLES for the windows builds (to match the others)
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.1-opt
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.1-opt
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.0-opt
-
- 15 Sep, 2007 3 commits
-
-
gshchepa@devsrv-b.mysql.com authored
Post-merge fix.
-
gshchepa@devsrv-b.mysql.com authored
into devsrv-b.mysql.com:/data0/gshchepa/mysql-5.1-opt
-
gshchepa@devsrv-b.mysql.com authored
Post-fix for bug#27695.
-
- 14 Sep, 2007 21 commits
-
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B31001-5.1-opt
-
gshchepa@devsrv-b.mysql.com authored
into devsrv-b.mysql.com:/data0/gshchepa/mysql-5.1-opt
-
gshchepa@devsrv-b.mysql.com authored
into devsrv-b.mysql.com:/data0/gshchepa/mysql-5.0-opt
-
joerg@trift2. authored
into trift2.:/MySQL/M51/push-5.1
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
joerg@trift2. authored
into trift2.:/MySQL/M51/push-5.1
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
joerg@trift2. authored
into trift2.:/MySQL/M41/push-4.1
-
sergefp@mysql.com authored
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B31001-5.0-opt
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/work/B31001-5.1-opt
-
gshchepa@devsrv-b.mysql.com authored
Merge with 5.0-opt.
-
gkodinov/kgeorge@magare.gmz authored
The optimizer sets index traversal in reverse order only if there are used key parts that are not compared to a constant. However using the primary key as an ORDER BY suffix rendered the check incomplete : going in reverse order must still be used even if all the parts of the secondary key are compared to a constant. Fixed by relaxing the check and set reverse traversal even when all the secondary index keyparts are compared to a const. Also account for the case when all the primary keys are compared to a constant.
-
sergefp@pylon.mylan authored
into mysql.com:/home/psergey/mysql-5.1-bug27927
-
sergefp@pylon.mylan authored
into mysql.com:/home/psergey/mysql-5.0-bug30324
-
sergefp@mysql.com authored
- The bug was caused by COUNT(DISTINCT ...) code using Unique object in a way that assumed that BIT(N) column occupies a contiguous space in temp_table->record[0] buffer. - The fix is to make COUNT(DISTINCT ...) code instruct create_tmp_table to create temporary table with column of type BIGINT, not BIT(N).
-
sergefp@pylon.mylan authored
into mysql.com:/home/psergey/mysql-5.1-bug27927
-
sergefp@mysql.com authored
- Introduced val_int_endpoint() function which converts between func argument intervals and func value intervals for monotonic functions. - Made partition interval analyzer use part_expr->val_int_endpoint() to check if the edge values should be included.
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-new-ndb-merge
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-new-ndb-merge
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.0-ndb-merge
-