mariadb

Tree: 19854c6d8c

Author	SHA1	Message	Date
Sergey Glukhov	19854c6d8c	Bug#43385 Cannot ALTER DATABASE ... UPGRADE DATA DIRECTORY NAME when Views exist(addon) mysql_rename_view can not rename view if database is not the same. The fix is to add new argument 'new_db' to mysql_rename_view() and allow rename with different databases (only for ALTER DATABASE ... UPGRADE DATA DIRECTORY NAME). mysql-test/t/upgrade.test: test fix sql/parse_file.cc: mysql_rename_view can not rename view if database is not the same. The fix is to add new argument 'new_db' to mysql_rename_view() and allow rename with different databases (only for ALTER DATABASE ... UPGRADE DATA DIRECTORY NAME). sql/parse_file.h: mysql_rename_view can not rename view if database is not the same. The fix is to add new argument 'new_db' to mysql_rename_view() and allow rename with different databases (only for ALTER DATABASE ... UPGRADE DATA DIRECTORY NAME). sql/sql_rename.cc: mysql_rename_view can not rename view if database is not the same. The fix is to add new argument 'new_db' to mysql_rename_view() and allow rename with different databases (only for ALTER DATABASE ... UPGRADE DATA DIRECTORY NAME). sql/sql_view.cc: mysql_rename_view can not rename view if database is not the same. The fix is to add new argument 'new_db' to mysql_rename_view() and allow rename with different databases (only for ALTER DATABASE ... UPGRADE DATA DIRECTORY NAME). sql/sql_view.h: mysql_rename_view can not rename view if database is not the same. The fix is to add new argument 'new_db' to mysql_rename_view() and allow rename with different databases (only for ALTER DATABASE ... UPGRADE DATA DIRECTORY NAME).	17 years ago
Narayanan V	2187c60bf4	merging with mysql-5.1-bugteam	17 years ago
Narayanan V	097262a85b	merging with mysql-5.1-bugteam tree	17 years ago
Narayanan V	af639a90ad	merging with mysql-5.1-bugteam tree	17 years ago
Chad MILLER	ebd4f43e44	Merge fix for bug 39559 and bugteam trunk.	17 years ago
Sergey Glukhov	bb08984f07	Bug#43385 Cannot ALTER DATABASE ... UPGRADE DATA DIRECTORY NAME when Views exist allow 'rename view' for ALTER ...UPGRADE DATA DIRECTORY NAME command. it's safe because a view has valid internal db&table names in this case. mysql-test/r/upgrade.result: test result mysql-test/t/upgrade.test: test case sql/sql_rename.cc: allow 'rename view' for ALTER ...UPGRADE DATA DIRECTORY NAME command. it's safe because a view has valid internal db&table names in this case.	17 years ago
Narayanan V	f286444bd5	Bug#44025 Some schema names longer than 8 characters not supported by IBMDB2I On IBM i 5.4, schemas with names that are longer than 8 characters and contain digits or an underscore cannot contain IBMDB2I tables, even though this should theoritically be possible if all alpha characters are uppercase. THe current patch fixes the IBMDB2I engine to allow digits and the underscore(_) to be used in schema names longer than 8 characters on IBM i 5.4. storage/ibmdb2i/db2i_misc.h: The function which detected whether the operating system would treat a schema as an "ordinary identifier" (allowing 10 characters in the name instead of 8) did not cover all possible cases.Function was renamed and enhanced to detect all possible cases of "ordinary identifiers". storage/ibmdb2i/ha_ibmdb2i.cc: use the renamed function to cover all possible cases of ordinary identifiers.	17 years ago
Narayanan V	63e2b7dd08	Bug#44022 CREATE TABLE sometimes fails silently for IBMDB2I engine In some circumstances, when a table is created with the IBMDB2I engine, the CREATE TABLE statement will return successfully but the table will not exist. The current patch addresses the above issue and causes CREATE to fail and report and error to the user. storage/ibmdb2i/ha_ibmdb2i.cc: Locally declared return code hid function- scoped declaration and went out of scope before being returned. Removed inner declaration.	17 years ago
Narayanan V	ee64a8d4f0	Bug#44020 Unicode Swedish collations not working with IBMDB2I The utf8_swedish_ci and ucs2_swedish_ci collations do not work with indexes on IBMDB2I tables. The current patch adds the mapping for ucs2_swedish collation and removes the ucs2_spanish2 mapping which is not supported by any version of the operating system. storage/ibmdb2i/db2i_collationSupport.cc: Removed mapping for ucs2_spanish2 collation since it is not supported by any version of the operating system. Added mapping for ucs2_swedish collation which had been overlooked but is supported by the IBM i 6.1.	17 years ago
Chad MILLER	8c828507e4	Bug#39559: dump of stored procedures / functions with C-style \ comment can't be read back A change to the lexer in 5.1 caused slash-asterisk-bang-version sections to be terminated early if there exists a slash-asterisk- style comment inside it. Nesting comments is usually illegal, but we rely on versioned comment blocks in mysqldump, and the contents of those sections must be allowed to have comments. The problem was that when encountering open-comment tokens and consuming -or- passing through the contents, the "in_comment" state at the end was clobbered with the not-in-a-comment value, regardless of whether we were in a comment before this or not. So, """/!VER one / two / three /""" would lose its in-comment state between "two" and "three". Save the echo and in-comment state, and restore it at the end of the comment if we consume a comment.	17 years ago
Davi Arnaut	214bd5a121	Bug#43706: libmysqld segfaults when re-intialised Bug#44091: libmysqld gets stuck waiting on mutex on initialization The problem was that libmysqld wasn't enforcing a certain initialization and deinitialization order for the mysys library. Another problem was that the global object used for management of log event handlers (aka LOGGER) wasn't being prepared for a possible reutilization. What leads to the hang/crash reported is that a failure to load the language file triggers a double call of the cleanup functions, causing an already destroyed mutex to be used. The solution is enforce a order on the initialization and deinitialization of the mysys library within the libmysqld library and to ensure that the global LOGGER object reset it's internal state during cleanup. mysys/my_init.c: Deinitialize only if initialized already. sql/log.cc: Reset state.	17 years ago
Luis Soares	8a41a0ba1f	manual merge: 5.0-bugteam --> 5.1-bugteam Note: empty changeset.	17 years ago
Luis Soares	84ae9ecab0	BUG#13684: SP: DROP PROCEDURE\|FUNCTION IF EXISTS not binlogged if routine does not exist There is an inconsistency with DROP DATABASE IF EXISTS, DROP TABLE IF EXISTS and DROP VIEW IF EXISTS: those are binlogged even if the DB or TABLE does not exist, whereas DROP PROCEDURE IF EXISTS does not. It would be nice or at least consistent if DROP PROCEDURE/STATEMENT worked the same too. Fixed DROP PROCEDURE\|FUNCTION IF EXISTS by adding a call to mysql_bin_log.write in mysql_execute_command. Checked also if all documented "DROP (...) IF EXISTS" get binlogged. NOTE: This is a 5.0 backport patch as requested by support. mysql-test/r/rpl_drop_if_exists.result: Result file for test case added. mysql-test/r/rpl_sp.result: Updated result file for existing test case that has now extra events in binary log (the ones from drop if exists procedure/function). mysql-test/t/rpl_drop_if_exists.test: Added test case for asserting validity of proposed patch. sql/sql_parse.cc: Added call mysql_bin_log.write when lex has drop_if_exists enabled for stored procedures.	17 years ago
Narayanan V	d0bc4e26a3	merging with mysql-5.1-bugteam	17 years ago
Sergey Glukhov	2711e1fa49	null merge	17 years ago
Sergey Glukhov	16d805c179	null merge	17 years ago
Sergey Glukhov	1db674f5c7	auotmerge	17 years ago
Sergey Glukhov	d2e6c462c8	5.0-bugteam->5.1-bugteam merge	17 years ago
He Zhenxing	ae439728f2	Null merge the fix only for 5.0-bugteam	17 years ago
Sergey Glukhov	920abd58b2	Bug#43833 Simple INSERT crashes the server The crash happens due to wrong 'digits' variable value(0), 'digits' can not be 0, so the fix is use 1 as min allowed value. mysql-test/r/insert.result: test result mysql-test/t/insert.test: test case sql/field.cc: The crash happens due to wrong 'digits' variable value(0), 'digits' can not be 0, so the fix is use 1 as min allowed value.	17 years ago
He Zhenxing	3b4ec32d45	Fix compile error on windows for BUG#37145 on 5.0-bugteam	17 years ago
Narayanan V	cce39fe8cf	merging with mysql-5.1-bugteam tree	17 years ago
Narayanan V	53f8922307	Bug#38848 myisam_use_mmap causes widespread myisam corruption on windows Currently the memory map is being created with a size that is greater than the size of the underlying datafile. This can cause varying behaviour, e.g. In windows the size of the datafile is increased, while on linux it remains the same. This fix removes the increment margin to the size that is used while creating the memory map. storage/myisam/mi_dynrec.c: remove MEMMAP_EXTRA_MARGIN that is used as the increment margin to the underlying datafile size while creating the mmap. storage/myisam/mi_packrec.c: The size of the underlying datafile is increased by MEMMAP_EXTRA_MARGIN when using a packed record format. Hence in this case the size of the memory map should be incremented by the same factor.	17 years ago
Anurag Shekhar	b1b8ab5159	merging with 5.0 bugteam tree	17 years ago
Anurag Shekhar	16e078f56c	merging with 5.0-bugteam tree.	17 years ago
He Zhenxing	c048216ebb	Null merge from 5.0-bugteam	17 years ago
He Zhenxing	3308a7f2fd	post fix compiling problem after push BUG#37145 to 5.0-bugteam	17 years ago
He Zhenxing	a15e25f852	Auto merge	17 years ago
He Zhenxing	caaa8531bd	Post fix of BUG#37145 Binlog the CREATE EVENT unless the created event been successfully dropped Modified Query_log_event constructor to make sure that error_code is not set to ER_SERVER_SHUTDOWN or ER_QUERY_INTERRUPTED errors when NOT_KILLED sql/events.cc: binlog the create event unless it's been successfully dropped sql/log_event.cc: Modified Query_log_event constructor to make sure that error_code is not set to ER_SERVER_SHUTDOWN or ER_QUERY_INTERRUPTED errors when NOT_KILLED	17 years ago
He Zhenxing	4ab0005be6	auto merge from 5.0-bugteam	17 years ago
He Zhenxing	1881ee2da5	auto merge	17 years ago
He Zhenxing	85cff45ef7	Manually merge BUG#37145 to 5.1-bugteam	17 years ago
Alfranio Correia	fb5bc0a39d	BUG#39393. Post-fix for test rpl_skip_error. The result set for multi-row statements is not the same between STMT and RBR and among different versions. Thus to avoid test failures, we are not printing out such result sets. Note, however, that this does not have impact on coverage and accuracy since the execution is able to continue without further issues when an error is found on the master and such error is set to be skipped.	17 years ago
Anurag Shekhar	dd0a6eb230	Bug #43950 myisamchk shows negative value for 'Max keyfile length' While printing the Max keyfile length 'llstr' call was used which was treating the max_key_file_length as negative. Changing this to ullstr fixes the problem. myisamchk output will differ in 32 bit and 64 bit Operating systems so its not possible to have test case for this bug. myisam/myisamchk.c: Replaced llstr by ullstr, while converting share->base.max_key_file_length-1 to string.	17 years ago
Alfranio Correia	43e85ecedf	merge 5.1-bugteam --> 5.1-bugteam (local)	17 years ago
He Zhenxing	16641a8820	Auto merge	17 years ago
Narayanan V	92aee5a6c6	Bug#37631 Incorrect key file for table after upgrading from 5.0 to 5.1 The conformance checker was not taking into account, and, making concessions for acceptable incompatibilites in tables created by versions earlier than 4.1. The current patch relaxes the conformance checker to ignore differences in key_alg and language for tables created by versions earlier than 4.1. storage/myisam/ha_myisam.cc: Modify check_definition to ignore differences in key_alg and language for tables created by versions earlier than 4.1.	17 years ago
Satya B	440858b816	merge to latest 5.1-bugteam	17 years ago
Satya B	55a149f29d	merge to latest 5.0-bugteam	17 years ago
Satya B	543abcd48e	merge 5.0-bugteam to 5.1-bugteam	17 years ago
Satya B	10350e2097	Fix for Bug #43973 - backup_myisam.test fails on 6.0-bugteam The test started failing following the push for BUG#41541. Some of the algorithms access bytes beyond the input data and this can affect up to one byte less than "word size" which is BITS_SAVED / 8. Fixed by adding (BITS_SAVED / 8) -1 bytes to buffer size (i.e. Memory Segment #2) to avoid accessing un-allocated data. myisam/mi_packrec.c: Fixed _mi_read_pack_info() method to allocate (BITS_SAVED/8) - 1 bytes to the Memory Segment #2 mysql-test/r/myisampack.result: Result file for BUG#43973 mysql-test/t/myisampack.test: Testcase for BUG#43973	17 years ago
Alexander Barkov	5847be8c9a	Bug#42649 THR_LOCK_charset global mutex abused by InnoDB The patch was originally proposed by Mikael and reviewed by Bar.	17 years ago
Satya B	58fa483a20	merge 5.0-bugteam to 5.1-bugteam	17 years ago
Alfranio Correia	e0d74efd85	merge 5.1-bugteam --> 5.1-bugteam (local)	17 years ago
Alfranio Correia	f9338b318e	BUG#39393 slave-skip-errors does not work when using ROW based replication RBR was not considering the option --slave-skip-errors. To fix the problem, we are reporting the ignored ERROR(s) as warnings thus avoiding stopping the SQL Thread. Besides, it fixes the output of "SHOW VARIABLES LIKE 'slave_skip_errors'" which was showing nothing when the value "all" was assigned to --slave-skip-errors. @sql/log_event.cc skipped rbr errors when the option skip-slave-errors is set. @sql/slave.cc fixed the output of for SHOW VARIABLES LIKE 'slave_skip_errors'" @test-cases fixed the output of rpl.rpl_idempotency updated the test case rpl_skip_error	17 years ago
Serge Kozlov	a81e21f8a4	Bug#37716. 1. Test case was rewritten completely. 2. Test covers 3 cases: a) do deadlock on slave, wait retries of transaction, unlock slave before lock timeout; b) do deadlock on slave and wait error 'lock timeout exceed' on slave; c) same as b) but if of max relay log size = 0; 3. Added comments inline. 4. Updated result file.	17 years ago
Davi Arnaut	54bf80b633	Merge Bug#43230 into mysql-5.1-bugteam	17 years ago
Davi Arnaut	72e978828e	Bug#43230: SELECT ... FOR UPDATE can hang with FLUSH TABLES WITH READ LOCK indefinitely The problem is that a SELECT .. FOR UPDATE statement might open a table and later wait for a impeding global read lock without noticing whether it is holding a table that is being waited upon the the flush phase of the process that took the global read lock. The same problem also affected the following statements: LOCK TABLES .. WRITE UPDATE .. SET (update and multi-table update) TRUNCATE TABLE .. LOAD DATA .. The solution is to make the above statements wait for a impending global read lock before opening the tables. If there is no impending global read lock, the statement raises a temporary protection against global read locks and progresses smoothly towards completion. Important notice: the patch does not try to address all possible cases, only those which are common and can be fixed unintrusively enough for 5.0. mysql-test/r/lock_multi.result: Add test case result for Bug#43230 mysql-test/t/lock_multi.test: Add test case for Bug#43230 sql/sql_lex.cc: Initialize flag. sql/sql_lex.h: Add a flag to the lexer. sql/sql_parse.cc: Wait for the global read lock is a write lock is going to be taken. The wait is done before opening tables. sql/sql_yacc.yy: Protect against the GRL if its a SELECT .. FOR UPDATE or LOCK TABLES .. WRITE statement.	17 years ago
Guangbao Ni	102de8f5c3	AutoMerged from pushbuild mysql-5.1-bugteam	17 years ago
Guangbao Ni	173d29536d	BUG#42640 mysqld crashes when unsafe statements are executed (STRICT_TRANS_TABLESmode) Mysql server crashes because unsafe statements warning is wrongly elevated to error, which is set the error status of Diagnostics_area of the thread in THD::binlog_query(). Yet the caller believes that binary logging shouldn't touch the status, so it will set the status also later by my_ok(), my_error() or my_message() seperately according to the execution result of the statement or transaction. But the status of Diagnostics_area of the thread is allowed to set only once. Fixed to clear the error wrongly set by binary logging, but keep the warning message. mysql-test/suite/binlog/r/binlog_stm_ps.result: Change unsafe warning to NOTE level mysql-test/suite/binlog/r/binlog_unsafe.result: Test case result for unsafe statements to ensure mysql sever don't crash mysql-test/suite/binlog/t/binlog_unsafe.test: Test case for unsafe statements to ensure mysql sever don't crash mysql-test/suite/rpl/r/rpl_skip_error.result: Change unsafe warning to NOTE level mysql-test/suite/rpl/r/rpl_stm_loadfile.result: Change unsafe warning to NOTE level mysql-test/suite/rpl/r/rpl_udf.result: Change unsafe warning to NOTE level sql/sql_class.cc: the error status of the thread is cleared When a warning is elevated to an error because of unsafe warning of binary log.	17 years ago

1 2 3 4 5 ...

57030 Commits (19854c6d8c66bc848774b8ee4ad433aa229465de) All Branches Search

57030 Commits (19854c6d8c66bc848774b8ee4ad433aa229465de)

All Branches