- 10 Feb, 2006 13 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 #17257 ndb, update fails for inner joins if tables do not have Primary Key change: the allocated area by setValue may not be around for later, store hidden key in special member variable instead
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.0
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.0
-
jonas@perch.ndb.mysql.com authored
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.0
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.0
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/50-work
-
jonas@perch.ndb.mysql.com authored
Introduce new variable c_newest_restorable_gci which is set _after_ both GCP_SAVE and COPY_GCI This variable is used when cutting redo (calcKeepGci) Also make sure complete GCI is run inbetween LCP's
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/50-work
-
jonas@perch.ndb.mysql.com authored
fix corruption due to page 0, file 0 gets released
-
ramil@mysql.com authored
into mysql.com:/usr/home/ram/work/5.0.b16511
-
- 09 Feb, 2006 7 commits
-
-
ramil@mysql.com authored
into mysql.com:/usr/home/ram/work/mysql-5.0
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-5.0
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0
-
msvensson@neptunus.(none) authored
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0
-
msvensson@neptunus.(none) authored
not needed by the tescases. This will save test time for those testcases that does not need cluster, but need a restart, as they dont have to wait the extra time it would take for cluster to restart. It will also save time for other testcases, as cluster does not need to be contacted for each table to be dropped or created. Backport from 5.1
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-5.0
-
- 08 Feb, 2006 6 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
-
ramil@mysql.com authored
Removed 'delayed' to make the test deterministic (as the bug itself has nothing to do with 'delayed').
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-5.0
-
ramil@mysql.com authored
into mysql.com:/usr/home/ram/work/5.0.b16511
-
- 07 Feb, 2006 14 commits
-
-
pekka@mysql.com authored
into mysql.com:/space/pekka/ndb/version/my50
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-5.0
-
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.
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-4.1
-
bell@sanja.is.com.ua authored
-
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
-