mariadb

Tree: b1dcf448ea

Author	SHA1	Message	Date
Alexander Nozdrin	c7d9455804	Merge from mysql-trunk.	16 years ago
Alexander Nozdrin	488f693c1b	Fix default.conf.	16 years ago
Alexander Nozdrin	516632890d	Auto-merge (empty) from mysql-trunk-bugfixing.	16 years ago
Alexander Nozdrin	b2554f59b1	Auto-merge from mysql-next-mr.	16 years ago
Alexander Nozdrin	9fe06befa0	Auto-merge from mysql-trunk.	16 years ago
Gleb Shchepa	897863813e	Bug #39653 : find_shortest_key in sql_select.cc does not consider clustered primary keys Choosing a shortest index for the covering index scan, the optimizer ignored the fact, that the clustered primary key read involves whole table data. The find_shortest_key function has been modified to take into account that fact that a clustered PK has a longest key of possible covering indices.	16 years ago
Tatiana A. Nurnberg	fd7bf5bcf7	auto-merge	16 years ago
Tatiana A. Nurnberg	f2a7a574a4	manual merge	16 years ago
Marc Alff	51f7f7f43e	Bug#45194 mysql_upgrade deletes existing data in performance_schema database/schema Before this fix, mysql_upgrade would always drop and re create the performance_schema database. This in theory could destroy user data created using 5.1 or older versions. With this fix, mysql_upgrade checks the content of the performance_schema database before droping it.	16 years ago
Guilhem Bichot	39e30ed9e0	Fix for BUG#51215 "log-error partially works with version 5.5": WL 4738 (reengineering of server variables) had broken the 5.1 behaviour of --log-error: --log-error without argument sent to stderr instead of writing to a file with an autogenerated name.	16 years ago
Ramil Kalimullin	c2b9fdb055	Fix for bug#32426: "FEDERATED query returns corrupt results for ORDER BY on a TEXT or VARCHAR field" backported to 5.1.	16 years ago
Alexander Nozdrin	dad94c24af	Make funcs_1.myisam_views experimental on Solaris due to Bug 50595.	16 years ago
Alexander Barkov	a45955793e	Fixing non-determenistic results.	16 years ago
Marc Alff	7ceb3b42e4	Bug#51738 Unit test pfs_instr-t crashes The unit test pfs_instr-t: - generates a very long (10,000) bytes file name - calls find_or_create_file. This leads to a buffer overflow in mysys in my_realpath(), because my_realpath and mysys file APIs in general do not test for input parameters: mysys assumes every file name is less that FN_REFLEN in length. Calling find_or_create_file with a very long file name is likely to happen when instrumenting third party code that does not use mysys, so this test is legitimate. The fix is to make find_or_create_file in the performance schema more robust in this case.	16 years ago
Marc Alff	f6a8202311	Bug#51741 Unit test pfs-t failing in mysql-next-mr-bugfixing The root cause of the failure is that when Bug#51447 performance schema evil twin files was fixed, instrumented file names got normalized. The pfs-t unit test depends on this file normalization, but it was not updated. This fix aligns pfs-t.cc lookup_file_by_name() with the logic in pfs_instr.cc find_or_create_file().	16 years ago
Mattias Jonsson	25596746db	Bug#50392: insert_id is not reset for partitioned tables auto_increment on duplicate entry The bug was that when INSERT_ID was used and the storage engine was told to release any reserved but not used auto_increment values, it set the highest auto_increment value to INSERT_ID. The fix was to check if the auto_increment value was forced by user (INSERT_ID) or by slave-thread, i.e. not auto- generated. So that it is only allowed to release generated values.	16 years ago
Georgi Kodinov	557ba4896b	Bug #51357 : crash when using handler commands on spatial indexes Spatial indexes were not checking for out-of-record condition in the handler next command when the previous command didn't found rows. Fixed by making the rtree index to check for end of rows condition before re-using the key from the previous search. Fixed another crash if the tree has changed since the last search. Added a test case for the other error.	16 years ago
Alexander Nozdrin	732103fcb5	Auto-merge from mysql-next-mr-bugfixing.	16 years ago
Alexander Nozdrin	2155847a29	Auto-merge from mysql-next-mr-bugfixing.	16 years ago
Joerg Bruehe	4667d673d6	Upmerge changes to "COPYING" (formatting, FSF addressi, still GPL v2 as of 1991) and "README" (header part: "This is a release of MySQL ...") from "trunk" to "next-mr".	16 years ago
Joerg Bruehe	e1a0e7b545	Update "README" (the list of contributed software and their licenses) by adding the header part "This is MySQL ...".	16 years ago
Joerg Bruehe	1d6f05b866	Upmerge the new formatting of "COPYING" from 5.1 to "trunk", the license remains to be the GPL Version 2, June 1991	16 years ago
Joerg Bruehe	fc4d400a3e	Use a new version of "COPYING", the GPL text. This is no change in contents, the differences are formatting only and an address update of the FSF. It continues to be Version 2, June 1991.	16 years ago
Tatiana A. Nurnberg	b1e6ccca56	auto-merge	16 years ago
Tatiana A. Nurnberg	3bf394b415	auto-merge	16 years ago
Tatiana A. Nurnberg	ef7f79eea9	auto-merge	16 years ago
Alexander Barkov	79cecfb55e	Bug#51675 Server crashes on inserting 4 byte char. after ALTER TABLE to 'utf8mb4' Bug#51676 Server crashes on SELECT, ORDER BY on 'utf8mb4' column An additional fix. We should use 0xFFFD as a weight for supplementary characters, not the "weight for character U+FFFD".	16 years ago
Mattias Jonsson	6e7539de29	Bug#50104: Partitioned table with just 1 partion works with fk There was no check for foreign keys when altering partitioned tables. Added check for FK when altering partitioned tables.	16 years ago
Alexander Barkov	19bda05a3c	Bug#51166 mysql client defaults to charset 'ascii' Using latin1 client character set for ASCII locales: - because ascii is not a build-in character set - for better backward compatibility	16 years ago
Mattias Jonsson	2d5c6b5bfe	Bug#48229: group by performance issue of partitioned table Problem was block_size on partitioned tables was not set, resulting in keys_per_block was not correct which affects the cost calculation for read time of indexes (including cost for group min/max).Which resulted in a bad optimizer decision. Fixed by setting stats.block_size correctly.	16 years ago
Alexander Barkov	2b0ff48baa	A joint patch for: Bug#51675 Server crashes on inserting 4 byte char. after ALTER TABLE to 'utf8mb4' Bug#51676 Server crashes on SELECT, ORDER BY on 'utf8mb4' column	16 years ago
Mattias Jonsson	71cc817b29	Bug#51347: assertion with show create table + partition by columns on decimal column The problem was that there was no check to disallow DECIMAL columns in the code (it was accepted as if it was INTEGER). Solution was to correctly disallow DECIMAL columns in COLUMNS partitioning. As documented.	16 years ago
Luis Soares	e831e729db	BUG#51055: Replication failure on duplicate key + traditional SQL mode When the master was executing in sql_mode='traditional' (which implies that really_abort_on_warning returns TRUE - because of MODE_STRICT_ALL_TABLES), the error code (ER_DUP_ENTRY in the reported case) was not being set in the Query_log_event. Therefore, even if a failure was to be expected when replaying the statement on the slave, a failure would occur, because the Query_log_event was not transporting the expected error code, but 0 instead. This was because when the master was getting the error code to set it in the Query_log_event, the executing thread would be assumed to have been killed: THD::killed==THD::KILL_BAD_DATA. This would make the error code fetch routine not to check thd->main_da.sql_errno(), but instead the thd->killed value. What's more, is that the server would thd->killed value if thd->killed == THD::KILL_BAD_DATA and return 0 instead. So this is a double inconsistency, as the we should not even check thd->killed but rather thd->main_da.sql_errno(). We fix this by extending the condition used to choose whether to check the thd->main_da.sql_errno() or thd->killed, so that it takes into consideration the case when: thd->killed==THD::KILL_BAD_DATA.	16 years ago
Horst.Hunger	37c3268cc1	Push the test to next-mr-bar2 to let them run in pushbuild.	16 years ago
Alexander Nozdrin	4f08c6d0e5	A follow-up on WL#5154 and WL#5182: remove forgotten options.	16 years ago
Vladislav Vaintroub	1befd1fb25	merge	16 years ago
Mattias Jonsson	af738870d4	Fix for debug print of null string (fails on pb for solaris debug_max)	16 years ago
Vladislav Vaintroub	c903a13e6a	merge	16 years ago
Luis Soares	24f7afe7bc	BUG#51226: mysqlbinlog replay: ERROR 1146 when using temp tables + failing statements Implicit DROP event for temporary table is not getting LOG_EVENT_THREAD_SPECIFIC_F flag, because, in the previous executed statement in the same thread, which might even be a failed statement, the thread_specific_used flag is set to FALSE (in mysql_reset_thd_for_next_command) and not set to TRUE before connection is shutdown. This means that implicit DROP event will take the FALSE value from thread_specific_used and will not set LOG_EVENT_THREAD_SPECIFIC_F in the event header. As a consequence, mysqlbinlog will not print the pseudo_thread_id from the DROP event, because one of the requirements for the printout is that this flag is set to TRUE. We fix this by setting thread_specific_used whenever we are binlogging a DROP in close_temporary_tables, and resetting it to its previous value afterward.	16 years ago
Vladislav Vaintroub	44084ea4b3	Fix a problem reported by Alik: when cmake is used for building in a symlinked directory, and confguration is later adjusted with "cmake-gui ." After it, GenServerSource fails with "no rule for <filename>". The reason for the error is that cmake-gui resolves "." as realpath and rules are generated accordingly, while "cmake" used symlinked path The fix uses ${CMAKE_CURRENT_BINARY_DIR} instead of ${CMAKE_BINARY_DIR}/sql for generated files. This causes CMake to use relative file names so relative file names when generating make rules. Using relative filenames avoids the problem of refering to the same directory using 2 different paths. Besides, using ${CMAKE_CURRENT_BINARY_DIR} is a commonly used style when working with generated files.	16 years ago
Vladislav Vaintroub	273d74eaa5	Bug #51488 :missing features and change behavior in cmake runs compared to autotools runs - Fix recognition of --with-debug=full in configure wrapper - Remove CMakeCache.txt in configure wrapper, to match the original - Fix recognition of max-no-ndb - Fix broken dependencies of mysql_fix_privilege_table.sql from mysql_system_tables.sql and mysql_system_tables_fix.sql - Add "distclean target" that informs user about appropriate bzr command	16 years ago
Sergey Vojtovich	1a9c3717f1	BUG#48265 - MRG_MYISAM problem (works in 5.0.85, does't work in 5.1.40) MERGE engine fails to open child table from a different database if child table/database name contains characters that are subject for table name to filename encoding (WL1324). Another problem is that MERGE engine didn't properly open child table from the same database if child table name contains characters like '/', '#'. The problem was that table name to file name encoding was applied inconsistently: * On CREATE: encode table name + database name if child table is in different database; do not encode table name if child table is in the same database; * No decoding on open. With this fix child table/database names are always encoded on CREATE and decoded on open. Compatibility with older tables preserved. Along with this patch comes fix for SHOW CREATE TABLE, which used to show child table/database path instead of child table/database names.	16 years ago
Jon Olav Hauglid	b59f88ee1f	Bug #51376 Assert `! is_set()' failed in Diagnostics_area::set_ok_status on DROP FUNCTION This assert tests that the server is not trying to send "ok" to the client if an error has occured during statement processing. In this case, the assert was triggered by lock timeout errors when accessing system tables to do an implicit REVOKE after executing DROP FUNCTION/PROCEDURE. In practice, this was only likely to happen with very low values for "lock_wait_timeout" (in the bug report 1 second was used). These errors were ignored and the server tried to send "ok" to the client, triggering the assert. The patch for Bug#45225 introduced lock timeouts for metadata locks. This made it possible to get timeouts when accessing system tables. Note that a followup patch for Bug#45225 pushed after this bug was reported, changed accessing of system tables such that the user-supplied timeout value is ignored and the maximum timeout value is used instead. This exact bug was therefore only noticeable in the period between the initial Bug#45225 patch and the followup patch. However, the same problem could occur for any errors during revoking of privileges - not just timeouts. This patch fixes the problem by making sure that any errors during revoking of privileges are reported to the client. Test case added to sp-destruct.test. Since the original bug is not reproducable now that system tables are accessed using a a long timeout value, this test instead calls DROP FUNCTION with a grant system table missing.	16 years ago
Tatiana A. Nurnberg	64cce948b8	auto-merge	16 years ago
Tatiana A. Nurnberg	fd7a531373	auto-merge	16 years ago
Tatiana A. Nurnberg	b4faea2aa0	manual merge	16 years ago
Tatiana A. Nurnberg	87b4d36e5c	Bug#48295: explain extended crash with subquery and ONLY_FULL_GROUP_BY sql If an outer query is broken, a subquery might not even get set up. EXPLAIN EXTENDED did not expect this and merrily tried to de-ref all of the half-setup info. We now catch this case and print as much as we have, as it doesn't cost us anything (doesn't make regular execution slower). backport from 5.1	16 years ago
Tatiana A. Nurnberg	ff7f4bb9fa	auto-merge	16 years ago
Alexander Nozdrin	81f857135a	Auto-merge (empty) from mysql-trunk-bugfixing.	16 years ago
Alexander Nozdrin	c17e266437	Manual merge from mysql-next-mr. Conflicts: - sql/sql_base.cc	16 years ago

... 4 5 6 7 8 ...

61669 Commits (b1dcf448ead09e9a70cf035f20ac0e1a168e79a6) All Branches Search

61669 Commits (b1dcf448ead09e9a70cf035f20ac0e1a168e79a6)

All Branches