- 04 Sep, 2007 3 commits
-
-
unknown authored
into weblab.(none):/home/marcsql/TREE/mysql-5.1-rt50-merge mysql-test/r/sp.result: Auto merged mysql-test/t/mysql.test: Auto merged mysql-test/t/query_cache.test: Auto merged mysql-test/t/sp.test: Auto merged sql/item_cmpfunc.h: Auto merged sql/rpl_utility.h: Auto merged sql/sql_base.cc: Auto merged sql/sql_cache.cc: Auto merged sql/sql_lex.cc: Auto merged sql/sql_lex.h: Auto merged
-
unknown authored
into adventure.(none):/home/thek/Development/cpp/mysql-5.1-runtime
-
unknown authored
into adventure.(none):/home/thek/Development/cpp/mysql-5.1-runtime sql/sql_cache.cc: Auto merged
-
- 03 Sep, 2007 8 commits
-
-
unknown authored
into station.:/mnt/raid/alik/MySQL/5.1-rt-build
-
unknown authored
into adventure.(none):/home/thek/Development/cpp/bug21074/my51-bug21074 sql/sql_cache.cc: Null merge
-
unknown authored
-
unknown authored
statement. mysql-test/suite/rpl/r/rpl_ps.result: Update result file.
-
unknown authored
c++config.h now has the following code: // For example, <windows.h> is known to #define min and max as macros... #undef min #undef max So, our defines in my_global.h are undefined when <new> header is included. Move definitions of min()/max() to the end of my_global.h.
-
unknown authored
into adventure.(none):/home/thek/Development/cpp/mysql-5.1-runtime sql/sql_cache.cc: Auto merged
-
unknown authored
into adventure.(none):/home/thek/Development/cpp/bug21074/my51-bug21074 sql/sql_cache.cc: Null merge
-
unknown authored
Invaldating a subset of a sufficiently large query cache can take a long time. During this time the server is efficiently frozen and no other operation can be executed. This patch addresses this problem by setting a time limit on how long time a dictionary access request can take before giving up on the attempt. This patch does not work for query cache invalidations issued by DROP, ALTER or RENAME TABLE operations. sql/sql_cache.cc: Changed mutex locking to a timed spinn lock. If access to query cache dictionary takes "a long time" (currently more than 0.1 seconds) the system fall backs on ordinary statement execution.
-
- 01 Sep, 2007 4 commits
-
-
unknown authored
into pilot.(none):/data/msvensson/mysql/mysql-5.1-new-maint
-
unknown authored
into pilot.(none):/data/msvensson/mysql/mysql-5.1-new-maint mysql-test/lib/mtr_misc.pl: Auto merged
-
unknown authored
into pilot.(none):/data/msvensson/mysql/mysql-5.0-maint mysql-test/lib/mtr_misc.pl: Auto merged
-
unknown authored
-
- 31 Aug, 2007 13 commits
-
-
unknown authored
into weblab.(none):/home/marcsql/TREE/mysql-5.1-30712 sql/log.cc: Auto merged sql/sql_base.cc: Auto merged
-
unknown authored
mysql-test/t/events.test: Wait for the select get_lock() to actually get the lock wait for release_lock() to actually release the lock
-
unknown authored
-
unknown authored
into ibm.opbmk:/home/alik/Documents/MySQL/devel/5.1-rt-bug25843 sql/mysql_priv.h: Auto merged sql/sp.cc: Auto merged sql/sp_head.cc: Auto merged sql/sql_class.cc: Auto merged sql/sql_class.h: Auto merged sql/sql_db.cc: Auto merged
-
unknown authored
-
unknown authored
of statement breaks binlog. There were two problems discovered by this bug: 1. Default (current) database is not fixed at the creation time. That leads to wrong output of DATABASE() function. 2. Database attributes (@@collation_database) are not fixed at the creation time. That leads to wrong resultset. Binlog breakage and Query Cache wrong output happened because of the first problem. The fix is to remember the current database at the PREPARE-time and set it each time at EXECUTE. mysql-test/include/query_cache_sql_prepare.inc: The first part of the test case for BUG#25843. mysql-test/r/query_cache_ps_no_prot.result: Update result file. mysql-test/r/query_cache_ps_ps_prot.result: Update result file. mysql-test/suite/rpl/r/rpl_ps.result: Update result file. mysql-test/suite/rpl/t/rpl_ps.test: The second part of the test case for BUG#25843. sql/mysql_priv.h: Added mysql_opt_change_db() prototype. sql/sp.cc: 1. Polishing; 2. sp_use_new_db() has been removed; 3. Use mysql_opt_change_db() instead of sp_use_new_db(). sql/sp.h: sp_use_new_db() has been removed. This function has nothing to do with a) sp and b) *new* database. It was merely "switch the current database if needed". sql/sp_head.cc: 1. Polishing. 2. Use mysql_opt_change_db() instead of sp_use_new_db(). sql/sql_class.cc: Move THD::{db, db_length} into Statement. sql/sql_class.h: Move THD::{db, db_length} into Statement. sql/sql_db.cc: Introduce mysql_opt_change_db() as a replacement (and inspired by) sp_use_new_db(). sql/sql_prepare.cc: 1. Remember the current database in Prepared_statement::prepare(). 2. Switch/restore the current database in Prepared_statement::execute().
-
unknown authored
into weblab.(none):/home/marcsql/TREE/mysql-5.1-cleanup
-
unknown authored
mysql-test/r/events.result: Fixed all the select on information_schema.processlist to be more reliable. mysql-test/t/events.test: Fixed all the select on information_schema.processlist to be more reliable.
-
unknown authored
-
unknown authored
-
unknown authored
into bodhi.(none):/opt/local/work/mysql-5.1-12713-new sql/handler.cc: Auto merged sql/log.cc: Auto merged
-
unknown authored
API instead. This is a pre-requisite of the fix for Bug 12713, which changes the data type of thd->ha_data from void * to struct Ha_data. include/mysql/plugin.h: Provide accessors to thd->ha_data for simple and robust code. sql/ha_ndbcluster_binlog.h: Use getters/setters of thd->ha_data, instead of direct access. sql/handler.cc: Use a getter of thd->ha_data instead of direct access. sql/log.cc: Use getters/setters of thd->ha_data, instead of direct access. sql/rpl_utility.h: Fix a compilation warning (declaration order must match initialization order in constructor). storage/federated/ha_federated.cc: Use interface accessors to thd->ha_data, instead of direct access.
-
unknown authored
Fix name of function in warning message. sql/item_timefunc.cc: Fix error message in extract_date_time(); ("str_to_time" -> "str_to_date")
-
- 30 Aug, 2007 12 commits
-
-
unknown authored
into weblab.(none):/home/marcsql/TREE/mysql-5.1-rt50-merge sql/sql_insert.cc: Auto merged
-
unknown authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/51
-
unknown authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/51
-
unknown authored
-
unknown authored
into weblab.(none):/home/marcsql/TREE/mysql-5.1-rt50-merge client/mysql.cc: Auto merged mysql-test/r/query_cache.result: Auto merged mysql-test/t/query_cache.test: Auto merged sql/item_cmpfunc.h: Auto merged sql/sp.cc: Auto merged sql/sp_head.cc: Auto merged sql/sql_class.h: Auto merged sql/sql_db.cc: Auto merged sql/sql_handler.cc: Auto merged sql/sql_lex.cc: Auto merged sql/sql_lex.h: Auto merged sql/sql_yacc.yy: Auto merged
-
unknown authored
mysql-test/r/insert_update.result: Post-merge: add test case result for Bug#28587. mysql-test/t/insert_update.test: Post-merge: add test case for Bug#28587.
-
unknown authored
into moksha.local:/Users/davi/mysql/push/bugs/28587-5.1 sql/sql_insert.cc: Auto merged
-
unknown authored
The problem is that a SELECT on one thread is blocked by INSERT ... ON DUPLICATE KEY UPDATE on another thread even when low_priority_updates is activated. The solution is to possibly downgrade the lock type to the setting of low_priority_updates if the INSERT cannot be concurrent. sql/sql_insert.cc: Possibly downgrade lock type to the the setting of low_priority_updates if if the INSERT cannot be concurrent.
-
unknown authored
into weblab.(none):/home/marcsql/TREE/mysql-5.1-rt50-merge
-
unknown authored
comments) This change set is for 5.1 (manually merged) Before this fix, the server would accept queries that contained comments, even when the comments were not properly closed with a '*' '/' marker. For example, select 1 /* + 2 <EOF> would be accepted as select 1 /* + 2 */ <EOF> and executed as select 1 With this fix, the server now rejects queries with unclosed comments as syntax errors. Both regular comments ('/' '*') and special comments ('/' '*' '!') must be closed with '*' '/' to be parsed correctly. mysql-test/r/comments.result: Unbalanced comments are a syntax error. mysql-test/t/comments.test: Unbalanced comments are a syntax error. sql/sql_lex.cc: Unbalanced comments are a syntax error.
-
unknown authored
generated so many warnings that the mode was unusable.
-
unknown authored
into weblab.(none):/home/marcsql/TREE/mysql-5.1-rt50-merge mysql-test/r/comments.result: failed auto merge mysql-test/t/comments.test: failed auto merge sql/sql_lex.cc: failed auto merge
-