- 17 Mar, 2006 4 commits
-
-
unknown authored
into calliope.local:/Volumes/Source/src/mysql-5.0__bug15846
-
unknown authored
vio/viosocket.c: ORs were wrong to begin with, but more importantly, we mustn't use shortable-circuit logic. Also newly reap the connection-closed event handle.
-
unknown authored
into mysql.com:/home/emurphy/src/mysql/bk-clean/mysql-5.0 sql/ha_innodb.cc: Auto merged
-
unknown authored
to binlog too much. When InnoDB has to rollback a transaction because the lock table has filled up, it also needs to inform the upper layer that the transaction was rolled back so that the cached transaction is not written to the binary log. sql/ha_innodb.cc: When InnoDB rolls back a transaction in HA_ERR_LOCK_TABLE_FULL, it needs to inform the upper layer to rollback the transaction also.
-
- 16 Mar, 2006 6 commits
-
-
unknown authored
into production.mysql.com:/usersnfs/abelkin/work-qc-5.0
-
unknown authored
into mysql.com:/usr/local/mysql/mysql-5.0 mysql-test/lib/mtr_timer.pl: Auto merged ndb/src/kernel/blocks/backup/Backup.cpp: Auto merged scripts/make_binary_distribution.sh: Auto merged
-
unknown authored
mysql-test/lib/mtr_timer.pl: Fix bug where ^C would trigger cleanup handler in both parent and timeout child processes, causing duplicated messages and potential conflicts.
-
unknown authored
into xiphis.org:/home/antony/work2/p1-bug14575.1
-
unknown authored
into shellback.(none):/home/msvensson/mysql/mysql-5.0
-
unknown authored
¨MySQL server crashes if you try to access to InnoDB table¨ crash caused by schizophrenic mysqld - 2 memory locations for logically same function with conflicting values. Fixed by backporting from 5.1 changes to have_xyz_db declarations. sql/mysql_priv.h: Backport have_xyz_db changes from 5.1 sql/mysqld.cc: Backport have_xyz_db changes from 5.1
-
- 15 Mar, 2006 1 commit
-
-
unknown authored
because it can couse problem with Query cache (BUG#14767) mysql-test/r/query_cache_notembedded.result: BUG#14767 test suite. mysql-test/t/query_cache_notembedded.test: BUG#14767 test suite. sql/sql_insert.cc: Query cache invalidation table we was inserting in just after unlocking table added to avoid the race condition as we had with SP. sql/sql_parse.cc: Query cache invalidation table we was inserting in just after unlocking table added to avoid the race condition as we had with SP. sql/sql_yacc.yy: We should prohibit concurent read of unserting file in SP because it can cause problem with query cache.
-
- 14 Mar, 2006 5 commits
-
-
unknown authored
into kite-hub.kitebird.com:/src/extern/MySQL/bk/mysql-5.0-r1.2084
-
unknown authored
Backport option description change from 5.1 to 5.0. sql/mysqld.cc: Backport option description change from 5.1 to 5.0.
-
unknown authored
Afterfix for bug#17366: Unchecked Item_int results in server crash sql/sql_select.cc: Afterfix for bug#17366: Unchecked Item_int results in server crash
-
unknown authored
- Add HAVE_OPENSSL and HAVE_YASSL to config-win.h include/config-win.h: Define HAVE_OPENSSL and HAVE_YASSL to make the server and client enable SSL support
-
unknown authored
into sunlight.local:/work_local/17336-bug-5.0-mysql mysql-test/r/subselect.result: Auto merged mysql-test/t/subselect.test: Auto merged
-
- 13 Mar, 2006 11 commits
-
-
unknown authored
When there is conjunction of conds, the substitute_for_best_equal_field() will call the eliminate_item_equal() function in loop to build final expression. But if eliminate_item_equal() finds that some cond will always evaluate to 0, then that cond will be substituted by Item_int with value == 0. In this case on the next iteration eliminate_item_equal() will get that Item_int and treat it as Item_cond. This is leads to memory corruption and server crash on cleanup phase. To the eliminate_item_equal() function was added DBUG_ASSERT for checking that all items treaten as Item_cond are really Item_cond. The substitute_for_best_equal_field() now checks that if eliminate_item_equal() returns Item_int and it's value is 0 then this value is returned as the result of whole conjunction. mysql-test/t/subselect.test: Added test for bug#17366: Unchecked Item_int results in server crash mysql-test/r/subselect.result: Added test for bug#17366: Unchecked Item_int results in server crash sql/sql_select.cc: Fixed bug#17366: Unchecked Item_int results in server crash To the eliminate_item_equal() function was added DBUG_ASSERT for checking that all items treaten as Item_cond are really Item_cond. The substitute_for_best_equal_field() now checks that if eliminate_item_equal() returns something other than Item_cond and if it is then this value is returned as the result of whole conjunction.
-
unknown authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.0 ndb/src/kernel/blocks/backup/Backup.cpp: Auto merged
-
unknown authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-4.1 ndb/src/kernel/blocks/backup/Backup.cpp: Auto merged
-
unknown authored
into perch.ndb.mysql.com:/home/jonas/src/50-work ndb/src/kernel/blocks/backup/Backup.cpp: Auto merged
-
unknown authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-4.1
-
unknown authored
ndb crash if trigger record get to big, fix incorrect max size of trigger record ndb/src/kernel/blocks/backup/Backup.cpp: Increase size of max trigger record
-
unknown authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.0
-
unknown authored
ndb crash if trigger record get to big, fix incorrect max size of trigger record ndb/src/kernel/blocks/backup/Backup.cpp: Increase size of max trigger record
-
unknown authored
into shellback.(none):/home/msvensson/mysql/mysql-5.0 mysql-test/mysql-test-run.pl: Auto merged
-
unknown authored
mysql-test/mysql-test-run.pl: Remove extra printouts
-
unknown authored
mysql-test/mysql-test-run.pl: Take a snapshot of the data dirs just after all db's have been installed and usedthat snasphot to restore the db(s) to a known state after a test case has failed. Thus avoiding subsequent test cases to fail because of previous test failures.
-
- 11 Mar, 2006 2 commits
- 10 Mar, 2006 11 commits
-
-
unknown authored
into mysql.com:/home/mydev/mysql-4.1-bug14980
-
unknown authored
into mysql.com:/home/mydev/mysql-5.0-bug14980
-
unknown authored
-
unknown authored
Now DEFINER-clause in stored routines is expected to appear in 5.0.20 release, not in 5.0.19. as it was supposed before. client/mysqldump.c: Fixing version. mysql-test/r/mysqldump.result: Updated the result file.
-
unknown authored
into mysql.com:/M50/merge-5.0
-
unknown authored
libmysql/libmysql.c: Auto merged tests/mysql_client_test.c: Auto merged
-
unknown authored
Fixes bug#15861 include/my_no_pthread.h: Even in a non-threaded build, some modules (at least "mysys/mf_keycache.c") need some type definitions provided by the system header file "pthread.h". Rather than add complexity to the code, include the header. Fixes bug#15861
-
unknown authored
into mysql.com:/usr_rh9/home/elkin.rh9/MySQL/FIXES/5.0.20-bug15101-sysdate
-
unknown authored
After the ChangeSet 1.1892.20.1 2005/08/24 (Bug #12562) SYSDATE() is not an alias of NOW() and is unsafe for replication. `SYSDATE()' backward compatible aliasing clashes with the idea #12562 fix. To make it safe-replicatable we have to either use RBR or to restore the pre-5.0 style. --sysdate-is-now command line flag was introduced to provide backward compatibility. sql/mysqld.cc: New option to force SYSDATE's backward compatible with 4.1 aliasing to NOW (not default) sql/sql_class.h: new slot to fill at init time and check at parse sql/sql_yacc.yy: calling NOW's branches when --sysdate-is-now mysql-test/r/sysdate_is_now.result: New BitKeeper file ``mysql-test/r/sysdate_is_now.result'' mysql-test/t/sysdate_is_now-master.opt: New BitKeeper file ``mysql-test/t/sysdate_is_now-master.opt'' mysql-test/t/sysdate_is_now.test: New BitKeeper file ``mysql-test/t/sysdate_is_now.test''
-
unknown authored
into mysql.com:/home/mydev/mysql-5.0-bug14980 include/my_base.h: Auto merged myisam/mi_delete.c: Auto merged myisam/mi_key.c: Auto merged myisam/mi_rnext_same.c: Auto merged myisam/mi_unique.c: Auto merged myisam/mi_update.c: Auto merged myisam/mi_write.c: Auto merged mysql-test/r/myisam.result: SCCS merged mysql-test/t/myisam.test: SCCS merged
-
unknown authored
For "count(*) while index_column = value" an index read is done. It consists of an index scan and retrieval of each key. For efficiency reasons the index scan stores the key in the special buffer 'lastkey2' once only. At the first iteration it notes this fact with the flag HA_STATE_RNEXT_SAME in 'info->update'. For efficiency reasons, the key retrieval for blobs does not allocate a new buffer, but uses 'lastkey2'... Now I clear the HA_STATE_RNEXT_SAME flag whenever the buffer has been polluted. In this case, the index scan copies the key value again (and sets the flag again). include/my_base.h: Bug#14980 - COUNT(*) incorrect on MyISAM table with certain INDEX Changed the comment for HA_STATE_RNEXT_SAME as a warning for future uses. myisam/mi_delete.c: Bug#14980 - COUNT(*) incorrect on MyISAM table with certain INDEX Removing the flag HA_STATE_RNEXT_SAME from info->update if info->lastkey2 was reused for another purpose than index scanning. myisam/mi_key.c: Bug#14980 - COUNT(*) incorrect on MyISAM table with certain INDEX Removing the flag HA_STATE_RNEXT_SAME from info->update if info->lastkey2 was reused for another purpose than index scanning. myisam/mi_rnext_same.c: Bug#14980 - COUNT(*) incorrect on MyISAM table with certain INDEX Removed trailing space and fixed a comment. myisam/mi_unique.c: Bug#14980 - COUNT(*) incorrect on MyISAM table with certain INDEX Removing the flag HA_STATE_RNEXT_SAME from info->update if info->lastkey2 was reused for another purpose than index scanning. myisam/mi_update.c: Bug#14980 - COUNT(*) incorrect on MyISAM table with certain INDEX Removing the flag HA_STATE_RNEXT_SAME from info->update if info->lastkey2 was reused for another purpose than index scanning. myisam/mi_write.c: Bug#14980 - COUNT(*) incorrect on MyISAM table with certain INDEX Removing the flag HA_STATE_RNEXT_SAME from info->update if info->lastkey2 was reused for another purpose than index scanning. mysql-test/r/myisam.result: Bug#14980 - COUNT(*) incorrect on MyISAM table with certain INDEX Added test result. mysql-test/t/myisam.test: Bug#14980 - COUNT(*) incorrect on MyISAM table with certain INDEX Added test.
-