mariadb

Tree: 54d36955b2

Author	SHA1	Message	Date
Sergey Vojtovich	f8b219ee29	BUG#36966 - mysqldump.test fails in pushbuild mysqldump.test is designed to run with concurrent inserts disabled. It is disabling concurrent inserts at the very beginning of the test case, and re-enables them at the bottom of the test. But for some reason (likely incorrect merge) we enable concurrent inserts in the middle of the test. The problem is fixed by enabling concurrent inserts only at the bottom of the test case.	17 years ago
Andrei Elkin	19fd076fb1	merge bug#38205 fixes to 5.1-bt	17 years ago
Satya B	3cac98cb93	Applying InnoDB snashot 5.1-ss3603. Fixes BUG#27276 1) BUG#27276 - InnoDB Error: ibuf cursor restoration fails 2) Follow up fix for BUG#27276 which fixes the bug introduced in the previous revision r2924 Detailed revision comments: r2924 \| marko \| 2008-10-29 10:07:48 +0200 (Wed, 29 Oct 2008) \| 7 lines branches/5.1: Merge revision 2866 from branches/zip: ibuf_delete_rec(): When the cursor to the insert buffer record cannot be restored, do not complain if the tablespace does not exist. (Bug #27276) Approved by Sunny Bains (rb://34) r3598 \| marko \| 2008-12-22 15:28:03 +0200 (Mon, 22 Dec 2008) \| 6 lines branches/5.1: ibuf_delete_rec(): When the record cannot be found and the tablespace has been dropped, commit the mini-transaction, so that InnoDB will not hold the insert buffer tree latch in exclusive mode, causing a potential deadlock. This bug was introduced in the fix of Bug #27276 in r2924.	17 years ago
Chad MILLER	4474300a05	Merge bugteam trunk and local.	17 years ago
Chad MILLER	04d83cc85c	Move test for bug 39559, which uses command-line mysql client to separate test file that doesn't permit mysqld embedded in mysqltest. Also, fix different comment handling in a incorrect new-to-5.1 test.	17 years ago
Georgi Kodinov	ed2d0035de	merged bug 35087 to 5.1-bugteam	17 years ago
Georgi Kodinov	0804479569	Bug #35087 : Inserting duplicate values at one time with DES_ENCRYPT leads to wrong results 3 problems found with DES_ENCRYPT/DES_DECRYPT : 1. The max length was not calculated properly. Fixed in fix_length_and_dec() 2. DES_ENCRYPT had a side effect of sometimes reallocating and changing the value of its argument. Fixed by explicitly pre-allocating the necessary space to pad the argument with trailing '*' (stars) when calculating the DES digest. 3. in DES_ENCRYPT the string buffer for the result value was not reallocated to the correct size and only string length was assigned to it. Fixed by making sure there's enough space to hold the result.	17 years ago
Sergey Glukhov	bf2e29d374	5.0-bugteam->5.1-bugteam merge	17 years ago
Sergey Glukhov	ff923cc82d	Bug#44151 using handler commands on information_schema tables crashes server information schema tables are based on internal tmp tables which are removed after each statement execution. So HANDLER comands can not be used with information schema. mysql-test/r/handler.result: test result mysql-test/t/handler.test: test case sql/sql_handler.cc: information schema tables are based on internal tmp tables which are removed after each statement execution. So HANDLER comands can not be used with information schema.	17 years ago
Anurag Shekhar	bd251400df	merging with local bugfix branch.	17 years ago
Anurag Shekhar	0501328a7d	Bug#44040 MySQL allows creating a MERGE table upon VIEWs but crashes when using it. The crash was due to a null pointer present for select_lex while processing the view. Adding a check while opening the view to see if its a child of a merge table fixed this problem. mysql-test/r/merge.result: Updated result for the new test case. mysql-test/t/merge.test: Added test case based on the bug description. sql/sql_base.cc: Added a check to check if the view being opened is a child table of a merge table and return error if it is.	17 years ago
Jonathan Perkin	086185089e	Merge from mysql-5.1.34-release	17 years ago
Patrick Crews	abd3f4cc0d	merge 5.0-> 5.1	17 years ago
Patrick Crews	5b05d360b0	Bug#26887 - main.count_distinct3 fails randomly Streamlined how we increase the size of our test table. The new method shows run time decreased by ~60%. This is not a guarantee that we will not see test timeouts (the random failures noted in the bug), but it should significantly reduce the chances of this occurring.	17 years ago
Georgi Kodinov	60083f4895	bumped the version to 5.0.82 (5.0.81-community to be released)	17 years ago
Satya B	24146bb2ab	BUG#40827 - Killing insert-select to MyISAM can cause table corruption Killing insert-select statement on MyISAM corrupts the table. Killing the insert-select statement corrupts the MyISAM table only when the destination table is empty and when it has indexes. When we bulk insert huge data and if the destination table is empty we disable the indexes for fast inserts, data is then inserted and indexes are re-enabled after bulk_insert operation Killing the query, aborts the repair table operation during enable indexes phase leading to table corruption. We now truncate the table when we detect that enable indexes is killed for bulk insert query.As we have an empty table before the operation, we can fix by truncating the table. mysql-test/r/myisam.result: Result file for BUG#40827 mysql-test/t/myisam.test: Testcase for BUG#40827 storage/myisam/ha_myisam.cc: Fixed end_bulk_insert() method to truncate the table when we detect enable index operation is killed.	17 years ago
unknown	6e0a64ef56	adjust version number	17 years ago
Staale Smedseng	3bea588ca1	Merge from 5.0-bugteam	17 years ago
Staale Smedseng	9301da563f	Bug#42430 Final commit to 5.0-bugteam	17 years ago
Alfranio Correia	c90a869c6b	auto-merge 5.1-bugteam --> 5.1-bugteam (local)	17 years ago
Satya B	c470d5e46e	Applying InnoDB snashot 5.1-ss4699, part 3. Fixes BUG#43660 1) BUG#43660 - SHOW INDEXES/ANALYZE does NOT update cardinality for indexes of InnoDB table Detailed revision comments: r4699 \| vasil \| 2009-04-09 14:01:52 +0300 (Thu, 09 Apr 2009) \| 15 lines branches/5.1: Fix Bug#43660 SHOW INDEXES/ANALYZE does NOT update cardinality for indexes of InnoDB table by replacing the PRNG that is used to pick random pages with a better one. This is based on r4670 but also adds a new configuration option and enables the fix only if this option is changed. Please skip the present revision when merging. Approved by: Heikki (via email)	17 years ago
Satya B	16c745053a	Applying InnoDB snashot 5.1-ss4699, part 2. Fixes BUG#43309 1) BUG#43309 - Test main.innodb can't be run twice 2) Follow up fix for BUG#43309, adds explanatory comments. Detailed revision comments: r4575 \| vasil \| 2009-03-30 15:55:31 +0300 (Mon, 30 Mar 2009) \| 8 lines branches/5.1: Fix Bug#43309 Test main.innodb can't be run twice Make the innodb mysql-test more flexible by inspecting how much a variable of interest has changed since the start of the test. Do not assume the variables have zero values at the start of the test. r4659 \| vasil \| 2009-04-06 15:34:51 +0300 (Mon, 06 Apr 2009) \| 6 lines branches/5.1: Followup to r4575 and the fix of Bug#43309 Test main.innodb can't be run twice: Add an explanatory comment, as suggested by Patrick Crews in the bug report.	17 years ago
Satya B	58c33f5514	Applying InnoDB snashot 5.1-ss4699, part 1. Fixes BUG#39320 and other problems 1) BUG#39320 - innodb crash in file btr/btr0pcur.c line 217 with innodb_locks_unsafe_for_binlog 2) Fixes bug in multi-table semi consistent reads. 3) Fixes email address from dev@innodb.com to innodb_dev_ww@oracle.com 4) Fixes warning message generated by main.innodb test Detailed revision comments: r4399 \| marko \| 2009-03-12 09:38:05 +0200 (Thu, 12 Mar 2009) \| 5 lines branches/5.1: row_sel_get_clust_rec_for_mysql(): Store the cursor position also for unlock_row(). (Bug #39320) rb://96 approved by Heikki Tuuri. r4400 \| marko \| 2009-03-12 10:06:44 +0200 (Thu, 12 Mar 2009) \| 8 lines branches/5.1: Fix a bug in multi-table semi-consistent reads. Remember the acquired record locks per table handle (row_prebuilt_t) rather than per transaction (trx_t), so that unlock_row should successfully unlock all non-matching rows in multi-table operations. This deficiency was found while investigating Bug #39320. rb://94 approved by Heikki Tuuri. r4481 \| marko \| 2009-03-19 15:01:48 +0200 (Thu, 19 Mar 2009) \| 6 lines branches/5.1: row_unlock_for_mysql(): Do not unlock records that were modified by the current transaction. This bug was introduced or unmasked in r4400. rb://97 approved by Heikki Tuuri r4573 \| vasil \| 2009-03-30 14:17:13 +0300 (Mon, 30 Mar 2009) \| 4 lines branches/5.1: Fix email address from dev@innodb.com to innodb_dev_ww@oracle.com r4574 \| vasil \| 2009-03-30 14:27:08 +0300 (Mon, 30 Mar 2009) \| 38 lines branches/5.1: Restore the state of INNODB_THREAD_CONCURRENCY to silence this warning: TEST RESULT TIME (ms) ------------------------------------------------------------ worker[1] Using MTR_BUILD_THREAD 250, with reserved ports 12500..12509 main.innodb [ pass ] 8803 MTR's internal check of the test case 'main.innodb' failed. This means that the test case does not preserve the state that existed before the test case was executed. Most likely the test case did not do a proper clean-up. This is the diff of the states of the servers before and after the test case was executed: mysqltest: Logging to '/tmp/autotest.sh-20090330_033000-5.1.5Hg8CY/mysql-5.1/mysql-test/var/tmp/check-mysqld_1.log'. mysqltest: Results saved in '/tmp/autotest.sh-20090330_033000-5.1.5Hg8CY/mysql-5.1/mysql-test/var/tmp/check-mysqld_1.result'. mysqltest: Connecting to server localhost:12500 (socket /tmp/autotest.sh-20090330_033000-5.1.5Hg8CY/mysql-5.1/mysql-test/var/tmp/mysqld.1.sock) as 'root', connection 'default', attempt 0 ... mysqltest: ... Connected. mysqltest: Start processing test commands from './include/check-testcase.test' ... mysqltest: ... Done processing test commands. --- /tmp/autotest.sh-20090330_033000-5.1.5Hg8CY/mysql-5.1/mysql-test/var/tmp/check-mysqld_1.result 2009-03-30 14:12:31.000000000 +0300 +++ /tmp/autotest.sh-20090330_033000-5.1.5Hg8CY/mysql-5.1/mysql-test/var/tmp/check-mysqld_1.reject 2009-03-30 14:12:41.000000000 +0300 @@ -99,7 +99,7 @@ INNODB_SUPPORT_XA ON INNODB_SYNC_SPIN_LOOPS 20 INNODB_TABLE_LOCKS ON -INNODB_THREAD_CONCURRENCY 8 +INNODB_THREAD_CONCURRENCY 16 INNODB_THREAD_SLEEP_DELAY 10000 INSERT_ID 0 INTERACTIVE_TIMEOUT 28800 mysqltest: Result content mismatch not ok r4576 \| vasil \| 2009-03-30 16:25:10 +0300 (Mon, 30 Mar 2009) \| 4 lines branches/5.1: Revert a change to Makefile.am that I committed accidentally in c4574.	17 years ago
Alfranio Correia	6736e5209a	BUG#41793 rpl_binlog_corruption disabled in main (needs new mtr) The test case was missing "let $slave_sql_errno= 1594;".	17 years ago
Joerg Bruehe	1b4cfc3632	Upmerge the fix of an error message typo (in "scripts/make_win_bin_dist") from 5.0 into 5.1	17 years ago
Joerg Bruehe	5a1124fa98	Just fix a silly typo in an error message ... scripts/make_win_bin_dist: Just fix a silly typo in an error message ... Change is so insignificant I even don't update the copyright year.	17 years ago
Joerg Bruehe	6782313c96	Merge some merge changesets from 5.0 up into 5.1-build (code changes have already been merged separately). Use this occasion to fix the branch name in the configuration file.	17 years ago
Chad MILLER	14f923c028	Merge 5.0.80 release and 5.0 community. Version left at 5.0.80.	17 years ago
Joerg Bruehe	14bd8b6587	Merge main 5.0 -> 5.0-build	17 years ago
Sergey Glukhov	3819daf064	Bug#41268 Help Text for \c is misleading in client command line interface(addon) fixed message for 'help' command client/mysql.cc: fixed message for 'help' command	17 years ago
Davi Arnaut	b27261a6f7	Bug#44164: TL_WRITE has no description in lock_descriptions[] The problem was that new lock types were being added without a corresponding description. Since the lock types (enum values) are used as indices to the description array, the descriptions could be shifted depending on the lock type. The solution is to ensure that every lock type has a correspondent description. include/thr_lock.h: Add warning. sql/sql_test.cc: Update lock descriptions.	17 years ago
Sergey Glukhov	f739349994	5.0-bugteam->5.1-bugteam merge	17 years ago
Tatiana A. Nurnberg	200865eb48	auto-merge	17 years ago
Tatiana A. Nurnberg	5d277dc986	auto-merge	17 years ago
Gleb Shchepa	5156c2d294	Bug #42563 : Message tells me to repair table though Storage Engine doesn't allow me to. In case of incompatible changes between old and new table versions, the mysqlcheck program prints error messages like this: error: Table upgrade required. Please do "REPAIR TABLE `table_name`" to fix it! However, InnoDB doesn't support REPAIR TABLE query, so the message is confusing. Error message text has been changed to: Table upgrade required. Please do "REPAIR TABLE `table_name`" or dump/reload to fix it!" mysql-test/r/repair.result: Updated test case for bug #42563. mysql-test/r/varbinary.result: Updated test case for bug #42563. sql/share/errmsg.txt: Bug #42563: Message tells me to repair table though Storage Engine doesn't allow me to. The ER_TABLE_NEEDS_UPGRADE error message has been changed to: Table upgrade required. Please do "REPAIR TABLE ``%-.32s`" or dump/reload to fix it!"	17 years ago
Narayanan V	0141da0444	Importing test cases for IBMDB2I The current patch -- Adds the ibmdb2i suite -- related include(.inc) files -- tests for Bug#44020 and Bug#44025	17 years ago
Joerg Bruehe	11e4e24bc7	Merge a tool change needed for cluster ("CGE") builds to achieve the correct package names ("scripts/make_binary_distribution.sh").	17 years ago
MySQL Build Team	bd2db28cda	Merge in missing changes from mysql-5.0.79-release	17 years ago
MySQL Build Team	a3b54b3744	Merge in changes from mysql-5.0.79-release branch	17 years ago
unknown	38e9e2f61e	Raise version number after cloning 5.0.80	17 years ago
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
Joerg Bruehe	8acca4388b	Merge the 5.1.31sp1 release back into the mainline. True to our way of doing QSP versions, this doesn't include any new changes but just backports of some important bug fixes that were also contained in version 5.1.32.	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

... 3 4 5 6 7 ...

57329 Commits (54d36955b2109d638d630366d91d88f37961ca6c) All Branches Search

57329 Commits (54d36955b2109d638d630366d91d88f37961ca6c)

All Branches