- 26 Nov, 2005 1 commit
-
-
knielsen@mysql.com authored
into mysql.com:/tmp/x/mysql-5.1-new
-
- 25 Nov, 2005 9 commits
-
-
eric@mysql.com authored
-
knielsen@mysql.com authored
into mysql.com:/data0/mysqldev/my/mysql-5.1.3-pushmain
-
holyfoot@deer.(none) authored
-
knielsen@mysql.com authored
into mysql.com:/data0/mysqldev/my/mysql-5.1.3-fixes
-
lenz@mysql.com authored
-
kent@mysql.com authored
-
knielsen@mysql.com authored
-
knielsen@mysql.com authored
-
mikael@mysql.com authored
The previous variant where it was a specific ha_partition method only worked for the partition handler. It was unfortunately called also for the NDB handler and in this case it called a random method in the NDB handler with random input.
-
- 24 Nov, 2005 22 commits
-
-
brian@zim.(none) authored
-
brian@zim.(none) authored
into zim.(none):/home/brian/mysql/mysql-5.1-new
-
brian@zim.(none) authored
Its funny, I am reading through the forums and someone asks "Can I please have a REPLACE INTO, instead an INSERT INTO?" and I remember how often I have used a sed script to modify MySQL dumps to have exactly that. So, use --replace and instead of getting INSERT INTO you will INSTEAD get REPLACE INTO. Buyer beward, REPLACE is a MySQL SQL, so you will not end up with a dump that can be used for other databases. Though I hear you could just use a sed line to modify it back :)
-
knielsen@mysql.com authored
Update version number to 5.1.4-alpha
-
tomas@poseidon.ndb.mysql.com authored
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-5.1
-
lenz@mysql.com authored
(only showed up in a non-debug build)
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1
-
monty@mysql.com authored
into mysql.com:/my/mysql-5.1
-
tomas@poseidon.ndb.mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.1-new
-
tomas@poseidon.ndb.mysql.com authored
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-5.1
-
tomas@poseidon.ndb.mysql.com authored
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-5.1-TDC
-
monty@mysql.com authored
-
monty@mysql.com authored
into mysql.com:/my/mysql-5.1
-
monty@mysql.com authored
Removed valgrind warnings when using not aligned bitmap buffer size Added setting of thread_stack
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-5.1-TDC
-
monty@mysql.com authored
into mysql.com:/my/mysql-5.1
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-5.1
-
monty@mysql.com authored
Larger stack size neaded for open table on x86 64 bit Fix failing test cases Deleted symlink from bk
-
- 23 Nov, 2005 8 commits
-
-
ranger@regul.home.lan authored
into regul.home.lan:/mnt/md/bk/mysql-5.0
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-5.1-TDC
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-5.1
-
monty@mysql.com authored
The table opening process now works the following way: - Create common TABLE_SHARE object - Read the .frm file and unpack it into the TABLE_SHARE object - Create a TABLE object based on the information in the TABLE_SHARE object and open a handler to the table object Other noteworthy changes: - In TABLE_SHARE the most common strings are now LEX_STRING's - Better error message when table is not found - Variable table_cache is now renamed 'table_open_cache' - New variable 'table_definition_cache' that is the number of table defintions that will be cached - strxnmov() calls are now fixed to avoid overflows - strxnmov() will now always add one end \0 to result - engine objects are now created with a TABLE_SHARE object instead of a TABLE object. - After creating a field object one must call field->init(table) before using it - For a busy system this change will give you: - Less memory usage for table object - Faster opening of tables (if it's has been in use or is in table definition cache) - Allow you to cache many table definitions objects - Faster drop of table
-
monty@mysql.com authored
into mysql.com:/my/mysql-5.1
-
konstantin@mysql.com authored
into mysql.com:/opt/local/work/mysql-5.0-root
-
konstantin@mysql.com authored
check_stack_overrun().
-
monty@mysql.com authored
Removed warnings that depends on floating point comparisions in type_newdecimal.test which caused failures in some setups
-