mariadb

Tree: c6b8dcedf9

Author	SHA1	Message	Date
Konstantin Osipov	c6b8dcedf9	A fix for Bug#44495 "Prepared Statement: CALL p(<x>) - `thd->protocol == &thd->protocol_text' failed" Do not assume that SQL prepared statements always run in text protocol. When invoked from a stored procedure, which is itself invoked by means of prepared CALL statement, the protocol may be binary. Juggle with the protocol only when we want to change it to binary in COM_STMT_EXECUTE, COM_STMT_PREPARE. This is a backport from 5.4/6.0, where the bug was fixed as part of WL#4264 "Backup: Stabilize Service Interface"	17 years ago
Staale Smedseng	03793f4c97	Merge from 5.1-bugteam	17 years ago
Georgi Kodinov	9752d4c866	automerge	17 years ago
Georgi Kodinov	e5ecb48125	automerge	17 years ago
Georgi Kodinov	924c8c5bfb	Addendum to the fix for bug #46080 : fixed the test case	17 years ago
Georgi Kodinov	7c5105599a	merge 5.1-main -> 5.1	17 years ago
Georgi Kodinov	2b4ec29274	merged 5.0-bugteam->5.1-bugteam	17 years ago
Georgi Kodinov	55f514ad05	fixed the CPU checking code.	17 years ago
Georgi Kodinov	af7d059586	merge 5.0-main -> 5.0-bugteam	17 years ago
Davi Arnaut	3e642d155e	Bug#21704: Renaming column does not update FK definition Remove commented-out test case. It has been moved to innodb_bug21704.test	17 years ago
Georgi Kodinov	5beae1f8dc	Bug #46080 : group_concat(... order by) crashes server when sort_buffer_size cannot allocate The NULL return from tree_insert() (on low memory) was not checked for in Item_func_group_concat::add(). As a result on low memory conditions a crash happens. Fixed by properly checking the return code.	17 years ago
Satya B	526a42e254	Applying InnoDB snapshot 5.1-ss5488,part 4. Fixes BUG#21704 1. BUG#21704 - Renaming column does not update FK definition 2. Changes in mysql-test/include/mtr_warnings.sql so that the testcase for BUG#21704 doesn't fail because of the warnings generated. Detailed revision comments: r5488 \| vasil \| 2009-07-09 19:16:44 +0300 (Thu, 09 Jul 2009) \| 13 lines branches/5.1: Fix Bug#21704 Renaming column does not update FK definition by checking whether a column that participates in a FK definition is being renamed and denying the ALTER in this case. The patch was originally developed by Davi Arnaut <Davi.Arnaut@Sun.COM>: http://lists.mysql.com/commits/77714 and was later adjusted to conform to InnoDB coding style by me (Vasil), I also added some more comments and moved the bug specific mysql-test to a separate file to make it more manageable and flexible.	17 years ago
Satya B	38d9fa8912	Applying InnoDB snapshot 5.1-ss5488 part3,Fixes BUG#45814 Detailed revision comments: r5440 \| vasil \| 2009-06-30 13:04:29 +0300 (Tue, 30 Jun 2009) \| 8 lines branches/5.1: Fix Bug#45814 URL reference in InnoDB server errors needs adjusting to match documentation by changing the URL from http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting.html to http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html	17 years ago
Satya B	c64b76edeb	Applying InnoDB snapshot 5.1-ss5488,part 2. Fixes BUG#45749 BUG#45749 - Race condition in SET GLOBAL innodb_commit_concurrency=DEFAULT Detailed revision comments: r5419 \| marko \| 2009-06-25 16:11:57 +0300 (Thu, 25 Jun 2009) \| 18 lines branches/5.1: Merge r5418 from branches/zip: ------------------------------------------------------------------------ r5418 \| marko \| 2009-06-25 15:55:52 +0300 (Thu, 25 Jun 2009) \| 5 lines Changed paths: M /branches/zip/ChangeLog M /branches/zip/handler/ha_innodb.cc M /branches/zip/mysql-test/innodb_bug42101-nonzero.result M /branches/zip/mysql-test/innodb_bug42101-nonzero.test M /branches/zip/mysql-test/innodb_bug42101.result M /branches/zip/mysql-test/innodb_bug42101.test branches/zip: Fix a race condition caused by SET GLOBAL innodb_commit_concurrency=DEFAULT. (Bug #45749) When innodb_commit_concurrency is initially set nonzero, DEFAULT would change it back to 0, triggering Bug #42101. rb://139 approved by Heikki Tuuri. ------------------------------------------------------------------------	17 years ago
Satya B	bb4778b57f	Applying InnoDB snashot 5.1-ss5488, part 1 1. Fixes build warnings caused by applying snapshot 5.1-ss5282 2. Fix the Makefile.am in storage/innobase to remove the header file 'fsp0types.h' which was added twice to fix build warning generated after applying the 5.1-ss5282 snapshot Detailed revision comments: r5410 \| marko \| 2009-06-24 22:26:34 +0300 (Wed, 24 Jun 2009) \| 2 lines branches/5.1: Add missing #include "mtr0log.h" to avoid warnings when compiling with -DUNIV_MUST_NOT_INLINE.	17 years ago
Staale Smedseng	ab2f3dd2a2	Bug #43397 mysql headers redefine pthread_mutex_init unnecessarily The problem is that libmysqlclient.so is built with THREAD undefined, while a client compiling against the same header files will see THREAD as defined and definitions in my_pthread.h will be included, possibly resulting in undefined symbols that cannot be resolved with libmysqlclient.so. The suggested solution is to require that clients wanting to link with libmysqlclient.so should be built with MYSQL_CLIENT_NO_THREADS defined. This requires a documentation change, and more details for this will be supplied if this patch is approved. The MYSQL_CLIENT_NO_THREADS define was renamed from UNDEF_THREADS_HACK, to get a more suitable (less suspicious) name for the define. (The UNDEF_THREADS_HACK is retained for backwards compatibility, though.) This patch is also in anticipation of WL#4958, which will remove this problem altogether by dropping the building of libmysqlclient.	17 years ago
Georgi Kodinov	8843026088	automerge	17 years ago
Georgi Kodinov	ead1ce94e6	Addendum to the fix for bug 45807 : initialize a member needed in Item_field::fix_fields()	17 years ago
Georgi Kodinov	c2ec53f94a	Bug#38998, Bug#46029, Bug#45243, Bug#46030 making tests experimental	17 years ago
Georgi Kodinov	5069a3e9ef	automerge	17 years ago
Georgi Kodinov	c8c22c7a98	Bug #40796 : adding the tests to the experimental pb2 set.	17 years ago
Patrick Crews	1eb64fa651	merge	17 years ago
Patrick Crews	61425acb3d	Bug#37746: Arithmetic range ("int") is smaller than expected Added code to the .test file to skip this test on Win64 for PB2 stability. Please remove this code when the bug is fixed.	17 years ago
Georgi Kodinov	d03714da6b	revert of hiding of the error exposed by this suite.	17 years ago
Georgi Kodinov	6a2f91bff4	merge of making bug 45578, 46010 and 45576 experimental in pb2.	17 years ago
Georgi Kodinov	7c681e9001	atuomerge	17 years ago
Georgi Kodinov	abfe915ac9	fixed compilation warnings on macosx	17 years ago
Georgi Kodinov	2275faa00e	fixed a failing test ctype_gbk_binlog : Table 't2' already exists	17 years ago
Georgi Kodinov	33380cf0b7	Bug #36259 (Optimizing with ORDER BY) and bug#45828 (Optimizer won't use partial primary key if another index can prevent filesort The fix for bug #28404 causes the covering ordering indexes to be preferred unconditionally over non-covering and ref indexes. Fixed by comparing the cost of using a covering index to the cost of using a ref index even for covering ordering indexes. Added an assertion to clarify the condition the local variables should be in. mysql-test/include/mix1.inc: Bug #36259: fixed a non-stable test case mysql-test/r/innodb_mysql.result: Bug #36259 and #45828 : test case mysql-test/t/innodb_mysql.test: Bug #36259 and #45828 : test case sql/sql_select.cc: Bug #36259 and #45828 : don't consider covering indexes supperior to ref keys.	17 years ago
V Narayanan	5ff7e35129	merging with mysql-5.1-bugteam	17 years ago
Andrei Elkin	22717a0459	Bug #44115 purge_relay_logs doesn't return an error when count_relay_log_space fails purge_relay_logs() did not propagate an error happend in count_relay_log_space(). Fixed with the suggestesd setting the error= true. Note, propagation generally out of purge_relay_logs() was fixed for Bug #44179, and the issue does not exist in 6.0 thanks to a patch for WL#2775. sql/rpl_rli.cc: the error is set on if count_relay_log_space(rli) fails.	17 years ago
V Narayanan	584fe5d625	merging with mysql-5.1-bugteam	17 years ago
Satya B	584e9f60d2	merge to mysql-5.1-bugteam branch	17 years ago
Davi Arnaut	a56ab623ba	Fix warnings generated by SunStudio and GCC. Based upon patch contributed by Stewart Smith mysql-test/lib/My/SafeProcess/safe_process.cc: Fix style -- remove unneeded spaces. Specify C linkage for the signal handling functions. Check return value from read()/write().	17 years ago
Satya B	02e70f1691	Bug#35111 - Truncate a MyISAM partitioned table does not reset the auto_increment value This is an alternative patch that instead of allowing RECREATE TABLE on TRUNCATE TABLE it implements reset_auto_increment that is called after delete_all_rows. Note: this bug was fixed by Mattias Jonsson: Pusing this patch: http://lists.mysql.com/commits/70370 mysql-test/suite/parts/r/partition_auto_increment_memory.result: Bug#35111: Truncate a MyISAM partitioned table does not reset the auto_increment value mysql-test/suite/parts/r/partition_auto_increment_myisam.result: Bug#35111: Truncate a MyISAM partitioned table does not reset the auto_increment value sql/ha_partition.cc: Bug#35111: Truncate a MyISAM partitioned table does not reset the auto_increment value Added reset_auto_increment, to be used after delete_all_rows to simulate truncate. storage/heap/ha_heap.cc: Bug#35111: Truncate a MyISAM partitioned table does not reset the auto_increment value Added reset_auto_increment, to be used after delete_all_rows to simulate truncate storage/heap/ha_heap.h: Bug#35111: Truncate a MyISAM partitioned table does not reset the auto_increment value Added reset_auto_increment, to be used after delete_all_rows to simulate truncate storage/myisam/ha_myisam.cc: Bug#35111: Truncate a MyISAM partitioned table does not reset the auto_increment value Added reset_auto_increment, to be used after delete_all_rows to simulate truncate. storage/myisam/ha_myisam.h: Bug#35111: Truncate a MyISAM partitioned table does not reset the auto_increment value Added reset_auto_increment, to be used after delete_all_rows to simulate truncate.	17 years ago
V Narayanan	2e8eb6ce94	Bug#45983 ibmdb2i_create_index_option=1 not working for primary key With ibmdb2i_create_index_option set to 1, creating an IBMDB2I table with a primary key should produce an additional index that uses EBCDIC hexadecimal sorting. However, this does not work. Adding indexes that are not primary keys does work. The ibmdb2i_create_index_option should be honoured when creating a table with a primary key. This patch adds code to the create() function to check for the value of the ibmdb2i_create_index_option variable and, when appropriate, to generate a HEX-based shadow index in DB2 for the primary key. Previously this behavior was limited to secondary indexes. Additionally, this patch restricts the creation of shadow indexes to cases in which a non-HEX sort sequence is used, as the documentation for ibmdb2i_create_index_option describes. Previously, the shadow index would in some cases be created even when the MySQL-specific index used HEX sorting, leading to redundant indexes. Finally, the code used to generate the list of fields for indexes and the code used to generate the SQL statement for the shadow indexes has been refactored into individual functions. mysql-test/suite/ibmdb2i/r/ibmdb2i_bug_45983.result: Bug#45983 ibmdb2i_create_index_option=1 not working for primary key Result file for the test case. mysql-test/suite/ibmdb2i/t/ibmdb2i_bug_45983.test: Bug#45983 ibmdb2i_create_index_option=1 not working for primary key Add tests to verify that the ibmdb2i_create_index_option is being honoured when creating a table with a primary key. storage/ibmdb2i/ha_ibmdb2i.cc: Bug#45983 ibmdb2i_create_index_option=1 not working for primary key - Add code to the create() function to check for the value of the ibmdb2i_create_index_option variable and, when appropriate, to generate a HEX-based shadow index in DB2 for the primary key. - Restrict the creation of shadow indexes to cases in which a non-*HEX sort sequence is used. - Refractor code used to generate the list of fields for indexes and the code used to generate the SQL statement for the shadow indexes into individual functions. storage/ibmdb2i/ha_ibmdb2i.h: Bug#45983 ibmdb2i_create_index_option=1 not working for primary key Add function prototypes for the functions that. - Generate the list of fields for indexes - Generate the SQL statement for the shadow indexes	17 years ago
unknown	006d97dc97	Raise version number after cloning 5.0.84	17 years ago
Georgi Kodinov	2a9da3fac5	tree name change	17 years ago
V Narayanan	6155562ca9	merging with mysql-5.1-bugteam.	17 years ago
Patrick Crews	869e6bd19f	Bug#44920: MTR2 is not processing master.opt input properly on Windows. Had attempted to disable this test on Windows only, but the nature of this bug does not allow for this. The master.opt file is processed before anything in in the actual test. As a result, we must use disabled.def files to ensure these tests are skipped on the problematic platforms. Removed Windows-only code and updated the proper disabled.def files accordingly.	17 years ago
Georgi Kodinov	05e498ea3d	null merged the disablement : problem is not present in 5.1	17 years ago
Georgi Kodinov	e92c681532	disable ndb_autodiscover2 : dependent on the disabled ndb_autodiscover	17 years ago
Georgi Kodinov	ba83235f42	Bug #45974 : disable test case in 5.1-bugteam	17 years ago
Georgi Kodinov	4c4109b35b	null-merged the test case disablement in bug 45972 to 5.1	17 years ago
Georgi Kodinov	9d94015b34	Bug#45972: disable the test case in 5.0	17 years ago
Georgi Kodinov	13306216c7	null-merged the disabled test cases.	17 years ago
Georgi Kodinov	c0ad792136	null-merge the mark of bug #38499 to big_test : it's running faster on 5.1	17 years ago
Georgi Kodinov	2a17098a60	Bug #35148 : ndb_autodiscover3 disabled	17 years ago
Georgi Kodinov	07e69e29ea	Bug #35148 : disabled testcase loaddata_autocom_ndb	17 years ago
Georgi Kodinov	fd709c8408	Bug #45521 : disabled the test case	17 years ago

1 2 3 4 5 ...

57741 Commits (c6b8dcedf91ddfe1cf9c4c114b0c42714238ac99) All Branches Search

57741 Commits (c6b8dcedf91ddfe1cf9c4c114b0c42714238ac99)

All Branches