- 08 Feb, 2006 1 commit
-
-
ramil@mysql.com authored
into mysql.com:/usr/home/ram/work/5.0.b16511
-
- 07 Feb, 2006 15 commits
-
-
pekka@mysql.com authored
into mysql.com:/space/pekka/ndb/version/my50
-
gunnar@mysql.com. authored
into mysql.com.:/data/BK/mysql-5.0
-
pekka@mysql.com authored
into mysql.com:/space/pekka/ndb/version/my50
-
pekka@mysql.com authored
-
pekka@mysql.com authored
-
gunnar@mysql.com. authored
into mysql.com.:/data/BK/mysql-5.0_8461_b
-
pekka@mysql.com authored
-
gunnar@mysql.com. authored
fix for bug#8461 BUG 8461 - TRUNCATE returns incorrect result if 2nd argument is negative Reason: Both TRUNCATE/ROUND converts INTEGERS to DOUBLE and back to INTEGERS Changed the integer routine to work on integers only. This bug affects 4.1, 5.0 and 5.1 Fixing in 4.1 will need to change the routine to handle different types individually. 5.0 did had different routines for different types already just the INTEGER routine was bad.
-
svoj@april.(none) authored
into april.(none):/home/svoj/devel/mysql/merge/mysql-5.0
-
svoj@april.(none) authored
into april.(none):/home/svoj/devel/mysql/merge/mysql-4.1
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0
-
tomas@poseidon.ndb.mysql.com authored
-
svoj@april.(none) authored
into april.(none):/home/svoj/devel/mysql/merge/mysql-4.1
-
svoj@april.(none) authored
into april.(none):/home/svoj/devel/mysql/merge/mysql-4.1
-
ramil@mysql.com authored
into mysql.com:/usr/home/ram/work/5.0.b16511
-
- 06 Feb, 2006 10 commits
-
-
tomas@poseidon.ndb.mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0
-
tomas@poseidon.ndb.mysql.com authored
Bug #17158 load data infile of char values into table of char with no (PK) fails to load Bug #17081 Doing "LOAD DATA INFILE" directly after delete can cause missing data
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-
igor@rurik.mysql.com authored
If check_quick_select returns non-empty range then the function cost_group_min_max cannot return 0 as an estimate of the number of retrieved records. Yet the function erroneously returned 0 as the estimate in some situations.
-
pem@mysql.com authored
into mysql.com:/extern/mysql/work/bug16303/mysql-5.0
-
pem@mysql.com authored
into mysql.com:/extern/mysql/work/bug16303/mysql-5.0
-
pem@mysql.com authored
-
pem@mysql.com authored
into mysql.com:/extern/mysql/work/bug16568/mysql-5.0
-
ramil@mysql.com authored
into mysql.com:/usr/home/ram/work/5.0.b16511
-
- 05 Feb, 2006 3 commits
-
-
pekka@mysql.com authored
-
pekka@mysql.com authored
into mysql.com:/space/pekka/ndb/version/my50
-
pekka@mysql.com authored
-
- 03 Feb, 2006 11 commits
-
-
pekka@mysql.com authored
into mysql.com:/space/pekka/ndb/version/my50
-
pekka@mysql.com authored
-
pekka@mysql.com authored
-
svoj@april.(none) authored
Fixed that fulltext query + union results in unexpected behaviour.
-
ramil@mysql.com authored
into mysql.com:/usr/home/ram/work/5.0.b16511
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-
igor@rurik.mysql.com authored
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-
igor@rurik.mysql.com authored
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-4.1-0
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/mysql-5.0
-