- 02 Dec, 2005 11 commits
-
-
unknown authored
-
unknown authored
Mark them properly as result-returning statements
-
unknown authored
-
unknown authored
used instead of column", the bug is to be fixed later. mysql-test/r/sp.result: Test results were fixed (Bug#5967)
-
unknown authored
After merge fix mysql-test/r/query_cache.result: After merge fix
-
unknown authored
mysql-test/r/update.result: Auto merged mysql-test/t/update.test: Auto merged ndb/src/kernel/blocks/backup/Backup.cpp: Auto merged sql/sql_update.cc: Auto merged
-
unknown authored
into moonbone.local:/work/15028-bug-4.1-mysql
-
unknown authored
into mysql.com:/usr/home/pem/bug14376/mysql-5.0 sql/sp_pcontext.cc: Auto merged sql/sql_yacc.yy: Auto merged mysql-test/r/sp.result: SCCS merged mysql-test/t/sp.test: SCCS merged sql/sp_pcontext.h: SCCS merged
-
unknown authored
sql/sp_pcontext.cc: Count boundary for variable visibility from the frame end instead. sql/sp_pcontext.h: Count boundary for variable visibility from the frame end instead. Updated comments. sql/sql_yacc.yy: Changed tabs to spaces.
-
unknown authored
ndb/src/kernel/blocks/backup/Backup.cpp: If crash 10018 is inserted on a 2 node cluster with fast CPU and slower disk, all nodes can respond with BACKUP_FRAGMENT_CONF for all fragments before the error in FSAPPENDCONF is hit. This would mean that no error code was set for the backup and that it would be incomplete as not all IO had been written to disk before the node crash. This would not be reported to the user. So the backup would appear to succeed but it really didn't. The window for this is rather small though. ndb/src/kernel/blocks/dbdict/Dbdict.cpp: Assert is incorrect for testBackup NFSlave test (causes crash insert 10015 to fail)
-
unknown authored
into mysql.com:/usr/home/ram/work/5.0.b12956 mysql-test/r/ps.result: Auto merged sql/item.cc: Auto merged sql/item.h: Auto merged sql/item_func.cc: Auto merged
-
- 01 Dec, 2005 12 commits
-
-
unknown authored
mysql-test/r/mysqldump.result: Fix results
-
unknown authored
depending on table order multi_update::send_data() was counting updates, not updated rows. Thus if one record have several updates it will be counted several times in 'rows matched' but updated only once. multi_update::send_data() now counts only unique rows. sql/sql_update.cc: Fix bug#15028 Multitable update returns different numbers of matched rows depending on table order multi_update::send_data() now counts only unique rows. mysql-test/t/update.test: Test case for bug#15028 Multitable update returns different numbers of matched rows depending on table order mysql-test/r/update.result: Test case for bug#15028 Multitable update returns different numbers of matched rows depending on table order
-
unknown authored
into mysql.com:/home/jimw/my/mysql-5.0-clean client/mysqldump.c: Auto merged mysql-test/r/mysqldump.result: Resolve conflicts mysql-test/t/mysqldump.test: Resolve conflicts
-
unknown authored
into mysql.com:/home/jimw/my/mysql-5.0-clean mysql-test/r/func_equal.result: Auto merged mysql-test/t/func_equal.test: Auto merged sql/item_cmpfunc.cc: SCCS merged
-
unknown authored
into mysql.com:/home/jimw/my/mysql-5.0-clean
-
unknown authored
mysql-test/r/bdb.result: Add new results mysql-test/r/innodb.result: Add new results mysql-test/t/bdb.test: Add simple test that large keys are allowed mysql-test/t/innodb.test: Add simple test that large keys are allowed sql/unireg.h: Allow key length of 3K even on 32-bit platforms
-
unknown authored
into selena.:H:/MYSQL/src/#14902-mysql-5.0 mysql-test/r/analyze.result: SCCS merged mysql-test/t/analyze.test: SCCS merged
-
unknown authored
to be in the query cache. (BUG#14652) mysql-test/r/query_cache.result: BUG#14652 test suite. mysql-test/t/query_cache.test: BUG#14652 test suite. sql/sql_cache.cc: We should skip beggining '(' characters when test query on possibility to be in the query cache.
-
unknown authored
into mysql.com:/usr/home/ram/work/mysql-5.0 sql/sql_class.cc: Auto merged sql/sql_class.h: Auto merged
-
unknown authored
Fix for bug #14304: auto_increment field incorrect set from within stored procedure (insert select). sql/sp_head.cc: Fix for bug #14304: auto_increment field incorrect set from within stored procedure (insert select). - call thd->cleanup_after_query() to clean next_insert_id. sql/sql_class.cc: Fix for bug #14304: auto_increment field incorrect set from within stored procedure (insert select). - save/restore clear_next_insert_id sql/sql_class.h: Fix for bug #14304: auto_increment field incorrect set from within stored procedure (insert select). - clear_next_insert_id added
-
unknown authored
into mysql.com:/home/timka/mysql/src/5.0-bug-14920 sql/sql_class.cc: Auto merged sql/sql_class.h: Auto merged sql/sql_select.cc: Auto merged mysql-test/r/group_min_max.result: Manually merged test cases. mysql-test/t/group_min_max.test: Manually merged test cases.
-
unknown authored
store TABLES.TABLE_TYPE in case of error during table opening mysql-test/r/information_schema.result: Fix for bug#14476 `information_schema`.`TABLES`.`TABLE_TYPE` with empty value test case mysql-test/t/information_schema.test: Fix for bug#14476 `information_schema`.`TABLES`.`TABLE_TYPE` with empty value test case
-
- 30 Nov, 2005 10 commits
-
-
unknown authored
into mysql.com:/home/jimw/my/mysql-5.0-clean
-
unknown authored
mysql-test/r/union.result: Fix order of test results
-
unknown authored
-
unknown authored
into mysql.com:/home/jimw/my/mysql-5.0-clean vio/viosslfactories.c: Auto merged
-
unknown authored
into mysql.com:/home/timka/mysql/src/5.0-virgin
-
unknown authored
into mysql.com:/home/gluh/MySQL/Merge/5.0 vio/viosslfactories.c: Auto merged
-
unknown authored
Commented out one failing query in the regression test (reported as a bug). mysql-test/r/join.result: Commented out failing query. mysql-test/t/join.test: Commented out failing query.
-
unknown authored
Implemented specialized regression test for the WL. mysql-test/r/join.result: Test results for natural join tests. mysql-test/t/join.test: Specialized test for natural join, and join ... on.
-
unknown authored
The cause of the bug was the use of end_write_group instead of end_write in the case when ORDER BY required a temporary table, which didn't take into account the fact that loose index scan already computes the result of MIN/MAX aggregate functions (and performs grouping). The solution is to call end_write instead of end_write_group and to add the MIN/MAX functions to the list of regular functions so that their values are inserted into the temporary table. mysql-test/r/group_min_max.result: Test for BUG#14920 mysql-test/t/group_min_max.test: Test for BUG#14920 sql/sql_class.cc: Added new member to TMP_TABLE_PARAM. sql/sql_class.h: Added new member to TMP_TABLE_PARAM. sql/sql_select.cc: Enable result rows generated by loose index scan being written into a temporary table. The change is necessary because loose index scan already computes the result of GROUP BY and the MIN/MAX aggregate functions. This is realized by three changes: - create_tmp_table allocates space for aggregate functions in the list of regular functions, - use end_write instead of end_write group, - copy the pointers to the MIN/MAX aggregate functions to the list of regular functions TMP_TABLE_PARAM::items_to_copy. sql/sql_select.h: New parameter to create_tmp_table.
-
unknown authored
- use rint() in some other val_int() methods as well.
-
- 29 Nov, 2005 7 commits
-
-
unknown authored
into mysql.com:/home/jimw/my/mysql-5.0-clean mysql-test/r/union.result: Auto merged sql/item.cc: Auto merged vio/viosslfactories.c: Auto merged mysql-test/t/union.test: Resolve conflict
-
unknown authored
into mysql.com:/home/jimw/my/mysql-4.1-clean sql/item.cc: Auto merged
-
unknown authored
into mysql.com:/home/alexi/dev/mysql-5.0-build
-
unknown authored
- use rint() in some other val_int() methods as well.
-
unknown authored
into mysql.com:/usr/local/mysql/mysql-5.0
-
unknown authored
mysql-test/r/type_ranges.result: result fixed
-
unknown authored
Removed warnings that depends on floating point comparisions in type_newdecimal.test which caused failures in some setups [Backported from mysql-5.1-new @1.1961.1.1] mysql-test/r/type_newdecimal.result: Moved long running query to type_newdecimal-big.test Removed warnings that depends on floating point comparisions [Backported from mysql-5.1-new] mysql-test/t/type_newdecimal.test: Moved long running query to type_newdecimal-big.test Removed warnings that depends on floating point comparisions [Backported from mysql-5.1-new]
-