mariadb

Tree: 10ae3ae1c8

Author	SHA1	Message	Date
Chad MILLER	10ae3ae1c8	Merge from 5.0-bugteam local.	18 years ago
Chad MILLER	ace51b79f1	Bug#30394: Empty HOME environment variable causes several utilities to crash Tilde expansion could fail when it was to expand to an empty string (such as when HOME is set to an empty string), especially on systems where size_t is unsigned.	18 years ago
Chad MILLER	780fee586d	Fix for bug#36399: Double free bug when INFORMATION_SCHEMA plugin init function fails Problem: if an INFORMATION_SCHEMA plugin initialization fails we free some inner plugin's data (schema_table) twice during the INSTALL PLUGIN command. Fix: free it once.	18 years ago
Chad MILLER	aa04d69e2d	Merge from bugteam trunk.	18 years ago
Chad MILLER	d5f5db8452	Merge from 5.0-bugteam local.	18 years ago
Chad MILLER	9f277e5554	Merge from 5.0-bugteam local.	18 years ago
Chad MILLER	3758804c69	Fix failing test case, re: bug 38195.	18 years ago
Chad MILLER	86fd86ed98	Merge from 5.0-bugteam.	18 years ago
Chad MILLER	21598ea0e6	Bug#37301 Length and Max_length differ with no obvious reason(2nd version) Length value is the length of the field, Max_length is the length of the field value. So Max_length can not be more than Length. The fix: fixed calculation of the Item_empty_string item length (Patch applied and queued on demand of Trudy/Davi.) sql/item.h: fixed calculation of the item length sql/sql_show.cc: removed unnecessary code	18 years ago
Chad MILLER	535a183964	Merge from 5.0-bugteam.	18 years ago
Chad MILLER	65c3870cfc	Bug#36270: incorrect calculation result - works in 4.1 but not in 5.0 or 5.1 When the fractional part in a multiplication of DECIMALs overflowed, we truncated the first operand rather than the longest. Now truncating least significant places instead for more precise multiplications. (Queuing at demand of Trudy/Davi.) mysql-test/r/type_newdecimal.result: show that if we need to truncate the scale of an operand, we pick the right one (that is, we discard the least significant decimal places) mysql-test/t/type_newdecimal.test: show that if we need to truncate the scale of an operand, we pick the right one (that is, we discard the least significant decimal places) strings/decimal.c: when needing to disregard fractional parts, pick the least significant ones	18 years ago
Chad MILLER	0156ccdc50	Merge from 5.0-bugteam.	18 years ago
Chad MILLER	2dcc449fab	Bug#21579 - innodb_concurrent random failures with varying differences Due to unknown changes the test failed in some ways. Fixed by checking the test case in detail, commenting the expected behavior, and fixing error directives. In the course of the analyze unneeded get_lock()/release_lock() use, unneeded send/reap use, and unneeded sleeps were removed. The lock wait timeout was reduced to 1 second, so that this is no big-test any more. The test was split into two parts, one running the tests with --innodb_locks_unsafe_for_binlog, the other part without. The main part (include/concurrent.inc) conditionally expects lock wait timeouts based on the value of the system variable innodb_locks_unsafe_for_binlog. The major part of the patch comes from Kristofer Pettersson. (Chad queues this patch on demand by Trudy/Davi.)	18 years ago
Chad MILLER	35c8b4c5e7	Bug#38272: timestamps fields incorrectly defaulted on \ update accross partitions. It's not Innodb-specific bug. ha_partition::update_row() didn't set table->timestamp_field_type= TIMESTAMP_NO_AUTO_SET when orig_timestamp_type == TIMESTAMP_AUTO_SET_ON_INSERT. So that a partition sets the timestamp field when a record is moved to a different partition. Fixed by doing '= TIMESTAMP_NO_AUTO_SET' unconditionally. Also ha_partition::write_row() is fixed in same way as now Field_timestamp::set() is called twice in SET_ON_INSERT case. (Chad queues this patch on demand by Trudy/Davi.) mysql-test/r/partition.result: Bug#38272 timestamps fields incorrectly defaulted on update accross partitions. test result mysql-test/t/partition.test: Bug#38272 timestamps fields incorrectly defaulted on update accross partitions. test case sql/ha_partition.cc: Bug#38272 timestamps fields incorrectly defaulted on update accross partitions. Do table->timestamp_field_type= TIMESTAMP_NO_AUTO_SET unconditionally in ha_partition::update_row and ::write_row()	18 years ago
Chad MILLER	0546add33e	Correcting tree name in bzr config. Should not include team suffix.	18 years ago
Davi Arnaut	986a27fb03	Merge from mysql-5.1 main.	18 years ago
Davi Arnaut	02cd785691	Bug#38560: valgrind warnings on PB due to query profiling Fix for a valgrind warning due to a jump on a uninitialized variable. The problem was that the sql profile preparation function wasn't being called for all possible code paths of query execution. The solution is to ensure that query profiling is always started before dispatch_command function is called and to explicitly call the profile preparation function on bootstrap. sql/sql_parse.cc: Finish query profiling properly when executing bootstrap commands. Add query profiling to execute_init_command as it calls dispatch_command.	18 years ago
Sergey Glukhov	02aaff1b34	Bug#36638 mysqld crashes when open file limit is passed and general query log enabled The problem: CSV storage engine open function returns success even thought it failed to open the data file The fix: return error Additional fixes: added MY_WME to my_open to avoid mysterious error message free share struct if open the file was unsuccessful mysql-test/r/csv.result: test result mysql-test/t/csv.test: test case storage/csv/ha_tina.cc: The problem: CSV storage engine open function returns success even thought it failed to open the data file The fix: return error Additional fixes: added MY_WME to my_open to avoid mysterious error message free share struct if open the file was unsuccessful	18 years ago
Ramil Kalimullin	2b179caf9a	Fix for bug #34779 : crash in checksum table on federated tables with blobs containing nulls Problem: FEDERATED SE improperly stores NULL fields in the record buffer. Fix: store them properly. mysql-test/r/federated.result: Fix for bug #34779: crash in checksum table on federated tables with blobs containing nulls - test result. mysql-test/t/federated.test: Fix for bug #34779: crash in checksum table on federated tables with blobs containing nulls - test case. sql/ha_federated.cc: Fix for bug #34779: crash in checksum table on federated tables with blobs containing nulls - storing a NULL field in the record buffer we must initialize its data as other code may rely on it.	18 years ago
Ramil Kalimullin	a233d7b851	Fix for bug#37537: myisamchk fails with Assertion failure with partitioned table Problem: missed "break" in a switch leads to unexpected assertion failure of 'myisamchk compressed_table'. Fix: add the break. storage/myisam/mi_check.c: Fix for bug#37537: myisamchk fails with Assertion failure with partitioned table In the record links check function (chk_data_link()) missed "break" for case COMPRESSED_RECORD was added.	18 years ago
Ramil Kalimullin	67a3d9e4d0	Fix for bug#37337: Function returns different results Problem: REGEXP in functions/PSs may return wrong results due to improper initialization. Fix: initialize required REGEXP params. sql/item_cmpfunc.cc: Fix for bug#37337: Function returns different results prev_regexp is used in the Item_func_regex::regcomp() to store previous regex and to avoid re-initialization if given the same pattern. Shoud be deleted in the Item_func_regex::cleanup() where we clean up the regexp structure.	18 years ago
He Zhenxing	e4e99f1439	auto merge	18 years ago
Evgeny Potemkin	368f7f63b2	Fixed failing test case for the bug#38195.	18 years ago
He Zhenxing	44f406a008	merge mysql-5.1-rpl-testfixes -> mysql-5.1	18 years ago
He Zhenxing	193a8f9735	fix after merge mysql-test/extra/rpl_tests/rpl_row_basic.test: remove extra sync_slave_with_master	18 years ago
He Zhenxing	84173b21e7	Merge with mysql-5.1-rpl-testfixes	18 years ago
He Zhenxing	ef58dcfcc8	auto merge	18 years ago
He Zhenxing	7bf8e29b99	Auto merge from mysql-5.1 main	18 years ago
He Zhenxing	29cc45d0ce	BUG#38290 valgrind warnings in binlog_base64_flag The problem was because the event allocated in mysql_client_binlog_statement was not freed when an error occured while applying the event. sql/sql_binlog.cc: Delete the event if apply it failed	18 years ago
Matthias Leich	03818bff5a	Merge	18 years ago
Matthias Leich	d23e8e06a1	Fix for Bug#37853 Test "funcs_1.processlist_val_ps" fails in various ways + corrections of logic in poll routines + minor improvements	18 years ago
Matthias Leich	632cf8ef43	Improve the testcases for Bug 12093 in ps_ddl.test Details: - add subtest with drop unrelated view - rearrange existing tests so that a distinction between drop procedure and drop function effects is possible	18 years ago
Serge Kozlov	f2188dc323	Bug#18817, removing --binlog-format option from .opt files	18 years ago
Mattias Jonsson	fd7c7e20af	Bug#20129: ALTER TABLE ... REPAIR PARTITION ... complains that partition is corrupt Post push fix an DBUG_ASSERT broke the embedded server, fixed by initializing it in the embedded version of Protocol_text::prepare_for_resend libmysqld/lib_sql.cc: Bug#20129: ALTER TABLE ... REPAIR PARTITION ... complains that partition is corrupt Post push fix an DBUG_ASSERT in Protocol_text::store broke the embedded server, fixed by initializing it in the embedded version of Protocol_text::prepare_for_resend	18 years ago
Evgeny Potemkin	b789b4f33c	Bug#38195: Incorrect handling of aggregate functions when loose index scan is used causes server crash. When the loose index scan access method is used values of aggregated functions are precomputed by it. Aggregation of such functions shouldn't be performed in this case and functions should be treated as normal ones. The create_tmp_table function wasn't taking this into account and this led to a crash if a query has MIN/MAX aggregate functions and employs temporary table and loose index scan. Now the JOIN::exec and the create_tmp_table functions treat MIN/MAX aggregate functions as normal ones when the loose index scan is used. mysql-test/r/group_min_max.result: Added a test case for the bug#38195. mysql-test/t/group_min_max.test: Added a test case for the bug#38195. sql/sql_select.cc: Bug#38195: Incorrect handling of aggregate functions when loose index scan is used causes server crash. Now the JOIN::exec and the create_tmp_table functions treat MIN/MAX aggregate functions as normal ones when the loose index scan is used.	18 years ago
Joerg Bruehe	e613615693	Null-merge a 5.0 version number change up to 5.1	18 years ago
Joerg Bruehe	182b238334	Correct the version number to 5.0.70. configure.in: Version number raise was incomplete, the 5.0 tree steps by 2.	18 years ago
unknown	6cab759d7a	Raise version number after cloning 5.0.68	18 years ago
Mattias Jonsson	c8d01f1401	Bug#37402: Mysql cant read partitioned table with capital letter in the name Post push fix (compiler warning) sql/ha_partition.cc: Bug#37402: Mysql cant read partitioned table with capital letter in the name fix to prevent a compiler warning.	18 years ago
Timothy Smith	88329eafd9	Up-merge from 5.0; adds test for innodb bug 34286 (but no code changes).	18 years ago
Mattias Jonsson	3cc5b2c571	merge (into the latest mysql-5.1-bugteam tree)	18 years ago
Timothy Smith	f1715b2b35	Merge in new test case	18 years ago
Timothy Smith	d7c36eb334	Merge some 5.0 innodb changes	18 years ago
Marc Alff	6c91a2805f	Merge mysql-5.1-bugteam -> local bugfix branch	18 years ago
Marc Alff	7ea370d2a2	Bug#38296 (low memory crash with many conditions in a query) This fix is for 5.1 only : back porting the 6.0 patch manually The parser code in sql/sql_yacc.yy needs to be more robust to out of memory conditions, so that when parsing a query fails due to OOM, the thread gracefully returns an error. Before this fix, a new/alloc returning NULL could: - cause a crash, if dereferencing the NULL pointer, - produce a corrupted parsed tree, containing NULL nodes, - alter the semantic of a query, by silently dropping token values or nodes With this fix: - C++ constructors are not executed with a NULL "this" pointer when operator new fails. This is achieved by declaring "operator new" with a "throw ()" clause, so that a failed new gracefully returns NULL on OOM conditions. - calls to new/alloc are tested for a NULL result, - The thread diagnostic area is set to an error status when OOM occurs. This ensures that a request failing in the server properly returns an ER_OUT_OF_RESOURCES error to the client. - OOM conditions cause the parser to stop immediately (MYSQL_YYABORT). This prevents causing further crashes when using a partially built parsed tree in further rules in the parser. No test scripts are provided, since automating OOM failures is not instrumented in the server. Tested under the debugger, to verify that an error in alloc_root cause the thread to returns gracefully all the way to the client application, with an ER_OUT_OF_RESOURCES error.	18 years ago
Davi Arnaut	b907f225fe	Merge and fix tree name.	18 years ago
Davi Arnaut	8ed209b21d	Merge and fix tree name.	18 years ago
Davi Arnaut	7e35139c8f	Merge mysql-5.0-bugteam into mysql-5.0	18 years ago
Mattias Jonsson	b32a49ac97	merge	18 years ago
Davi Arnaut	f18bc40caa	Merge mysql-5.1-bugteam into mysql-5.1 main.	18 years ago

1 2 3 4 5 ...

54599 Commits (10ae3ae1c8f7fe3a91caf4e1eeeefe34a9343b54) All Branches Search

54599 Commits (10ae3ae1c8f7fe3a91caf4e1eeeefe34a9343b54)

All Branches