- 25 Mar, 2011 6 commits
-
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-
Georgi Kodinov authored
Added back the specific warning number.
-
Luis Soares authored
-
Georgi Kodinov authored
ARE NOT BEING HONORED max_allowed_packet works in conjunction with net_buffer_length. max_allowed_packet is an upper bound of net_buffer_length. So it doesn't make sense to set the upper limit lower than the value. Added a warning (using ER_UNKNOWN_ERRROR and a specific message) when this is done (in the log at startup and when setting either max_allowed_packet or the net_buffer_length variables) Added a test case. Fixed several tests that broke the above rule.
-
- 24 Mar, 2011 4 commits
-
-
Luis Soares authored
Removing the test case from mysql-5.5 list of disabled test cases for the binlog suite. Actually, the test does not exist in mysql-5.5, thus this is just a clean up.
-
Luis Soares authored
Original patch did not remove the test case from the list of disabled test cases. Removing it now!
-
Luis Soares authored
-
Luis Soares authored
The slave was not able to find the correct row in the innodb table, because the row fetched from the innodb table would not match the before image. This happened because the (don't care) bytes in the NULLed fields would change once the row was stored in the storage engine (from zero to the default value). This would make bulk memory comparison (using memcmp) to fail. We fix this by taking a preventing measure and avoiding memcmp for tables that contain nullable fields. Therefore, we protect the slave search routine from engines that return arbitrary values for don't care bytes (in the nulled fields). Instead, the slave thread will only check null_bits and those fields that are not set to NULL when comparing the before image against the storage engine row. mysql-test/extra/rpl_tests/rpl_record_compare.test: Added test case to the include file so that this is tested with more than one engine. mysql-test/suite/rpl/r/rpl_row_rec_comp_innodb.result: Result update. mysql-test/suite/rpl/r/rpl_row_rec_comp_myisam.result: Result update. mysql-test/suite/rpl/t/rpl_row_rec_comp_myisam.test: Moved the include file last, so that the result from BUG#11766865 is not intermixed with the result for BUG#11760454. sql/log_event.cc: Skips memory comparison if the table has nullable columns and compares only non-nulled fields in the field comparison loop.
-
- 23 Mar, 2011 4 commits
-
-
Georgi Kodinov authored
Initialized correctly the have_innodb variable so that when the plugin is not initialized it stays "disabled" instead of "yes". Test suite added.
-
Bjorn Munch authored
-
Bjorn Munch authored
-
Bjorn Munch authored
-
- 22 Mar, 2011 12 commits
-
-
Magne Mahre authored
-
Magne Mahre authored
-
Magne Mahre authored
Didn't build on Solaris.
-
Bjorn Munch authored
-
Bjorn Munch authored
-
Bjorn Munch authored
-
Magne Mahre authored
-
Magne Mahre authored
-
Magne Mahre authored
The LGPL license is used in some legacy code, and to adhere to current licensing polity, we remove those files that are no longer used, and reorganize the remaining LGPL code so it will be GPL licensed from now on. Note: This patch only removed LGPL licensed files in MySQL 5.0, and is the first of a set of patches to remove LGPL from all trees. (See Bug# 11840513 for details) include/my_compare.h: Mostly code moved in from my_handler include/my_global.h: AIX-only code. Function used to be in my_port.c Inlining instead. libmysql/Makefile.shared: my_gethostbyname and my_port is removed myisam/mi_check.c: ha_find_null is moved from my_handler and made static.
-
Alexander Nozdrin authored
prepared statements with cursor protocol). The problem was a bug in Materialized-cursor implementation. Materialized_cursor::open() called send_result_metadata() with items pointing to already closed table. The fix is to send metadata when the table is still open. NOTE: this is a "partial" fix: metadata are different with and without --cursor-protocol, but that's a different large problem, one indication of which is reported as Bug 24176.
-
Georgi Kodinov authored
-
Vinay Fisrekar authored
Bug#11766500 - 59624: FUNCS_1 SUITE TESTS FAILING WITH RESULT DIFFERENCE WHEN RUN USING EMBEDDED MODE Updating result file for embedded mode tests due to recent changes
-
- 21 Mar, 2011 7 commits
-
-
Mayank Prasad authored
-
Mayank Prasad authored
Issue: ------ Due to prefix match, database like 'k' was matching with 'ka' and events of 'ka' we getting displayed for 'show event' of 'k'. Resolution: ----------- Scan for listing of events in a schema is made to be done on exact match of database (schema) name instead of just prefix. mysql-test/r/events_bugs.result: modified expected file with the expected results. mysql-test/t/events_bugs.test: added a test case to reproduce the scenario. sql/event_db_repository.cc: Scan for schema name is made to be done on exact db name match.
-
Georgi Kodinov authored
Fixed the author and the copyright.
-
MySQL Build Team authored
-
MySQL Build Team authored
-
Ramil Kalimullin authored
-
Ramil Kalimullin authored
-
- 18 Mar, 2011 7 commits
-
-
Georgi Kodinov authored
-
Bjorn Munch authored
-
Georgi Kodinov authored
configuration wizard to fail Made the fields mysql.user.plugin and mysql.user.authentication_string nullable to conform with some older clients doing inserts instead of using the commands.
-
Tor Didriksen authored
-
Vinay Fisrekar authored
+ Bug#11766500 - 59624: FUNCS_1 SUITE TESTS FAILING WITH RESULT DIFFERENCE WHEN RUN USING EMBEDDED MODE Updating result files for embedded mode
-
Bjorn Munch authored
The condition cursor-protocol => ps-protocol was done at "current setting" level" Moved it to "set by command line" level
-
Vinay Fisrekar authored
Bug#11766500 - 59624: FUNCS_1 SUITE TESTS FAILING WITH RESULT DIFFERENCE WHEN RUN USING EMBEDDED MODE Updating result files
-