mariadb

Tree: de91727eec

Author	SHA1	Message	Date
Kent Boortz	de91727eec	- Changes needed to use newer WiX version (Bug#60029) - Added an alterantive search path for WiX components - Added a custom welcome dialog to include the copyright line (Bug#59805 and Bug#59512) - Excluded some binaries to make package smaller, in effect makig the "essentials" package obsolete - Added a bit more error checking when running the WiX tools WiX XML changes done by Johannes Taxacher	15 years ago
Andrei Elkin	68e6a24d1c	Bug 12535301 - SYS_VARS.RPL_INIT_SLAVE_FUNC MISMATCHES IN DAILY-5.5 notifying PB2 the test fails through mysql-test/collections/default.experimental.	15 years ago
Alexander Nozdrin	19523cae6f	Ignore auto-generated files.	15 years ago
Alexander Nozdrin	da96e91524	A patch for Bug#12429877: QUERY_TABLES_LIST::SROUTINES IS NOT FREED IN FLUSH_READ_LOCK (VALGRIND WARNING). The problem was that under some circustances the memory allocated for Query_tables_list::sroutines was not freed properly. The cause of this problem was the absence of LEX::restore_backup_query_tables_list() call in one of the branches in mysql_table_grant() function.	15 years ago
Vinay Fisrekar	0c1e38b371	Merge from mysql-5.1 to mysql-5.5	15 years ago
Vinay Fisrekar	4731736320	Adding bug scenario for data types in main suite Impementing Test Review Comment. Bug test scenario: SELECT is not returning result set for "equal" (=) and "NULL safe equal operator" (<=>) on BIT data type. Extending this scenario for all data types	15 years ago
Bjorn Munch	0b9682a0ae	null upmerge	15 years ago
Bjorn Munch	db4ed17587	merge from 5.1-mtr	15 years ago
Bjorn Munch	0fb541fbb9	merge from 5.5-mtr	15 years ago
MySQL Build Team	33b015f30b	changed the VERSION tag to 14	15 years ago
chuck.bell@oracle.com	44b2df4aba	BUG#12549572 : CMake file does not include gcov option This patch inserts an 'ENABLE_GCOV' option for enabling gcov compilation on Linux machines. It modifies the CMakeLists.txt setting this option to 'OFF' by default. Note: The option requires a debug build. For example, -DCMAKE_BUILD_TYPE:string="Debug"	15 years ago
Bjorn Munch	e484f38435	null upmerge	15 years ago
Bjorn Munch	11a509bedf	null upmerge	15 years ago
Bjorn Munch	aa8715e15e	merge from 5.5 main	15 years ago
Jon Olav Hauglid	7577c115a0	Bug#12346411 SQL/LOG.CC:6509: ASSERTION `PREPARED_XIDS > 0' FAILED This assert could be triggered during two phase commit if binary log was used as transaction coordinator log. The triggered assert checks that the same number of transaction IDs are processed in the prepare and commit phases. The reason it was triggered, was that the transaction consisted of an INSERT/UPDATE IGNORE that had an ignorable error. Since it had an error, no row log events were made and therefore prepared_xids was 0. However, since it was an IGNORE statement, the statement started a read/write statement transaction, committed it and completed successfully. This patch fixes the problem by adjusting the assert to take this possibility into account. Test case added to binlog.binlog_innodb_row.test.	15 years ago
Tatjana Azundris Nuernberg	e72473450e	auto-merge	15 years ago
Bjorn Munch	dca22eb6f3	merge from 5.1 main	15 years ago
Tatjana Azundris Nuernberg	f1bad788e5	auto-merge	15 years ago
Tatjana Azundris Nuernberg	614f05e4ca	auto-merge	15 years ago
Tatjana Azundris Nuernberg	6fb68a22bd	Bug#11902767/Bug#60580: Statement improperly replicated crashes slave SQL thread If LOAD DATA INFILE featured a SET clause, the name=value pairs would be regenerated using item::print. Unfortunately, that code is mostly optimized for EXPLAIN EXTENDED output and such, and can not be relied on to return valid SQL. We now name each value its original, user-supplied form and use that to create LOAD DATA INFILE statements for statement-based replication.	15 years ago
Tatjana Azundris Nuernberg	25abeed586	auto-merge	15 years ago
Tatjana Azundris Nuernberg	79c1c8e586	auto-merge	15 years ago
Tatjana Azundris Nuernberg	a0f300a6d3	auto-merge Bug#11762799/Bug#55436	15 years ago
Tatjana Azundris Nuernberg	2683078d28	auto-merge Bug#11762799/Bug#55436	15 years ago
Luis Soares	efc20dca00	BUG#12416700 Automerged bzr bundle from bug report into latest mysql-5.5.	15 years ago
Magnus Blåudd	d8a9b36b9d	Merge bug 12384993	15 years ago
Alexander Nozdrin	cbf455cf87	Ignore auto-generated files.	15 years ago
Georgi Kodinov	621dc09548	merge from mysql-5.5	15 years ago
MySQL Build Team	94f424652c	Cloning of the 5.5.13 release from Mysql-5.5, increase the version number by two	15 years ago
Georgi Kodinov	a914a32191	Bug #11744875 : 4082: integer lengths cause truncation with distinct concat and innodb The 5.5 version of the patch. The server doesn't restrict the data that can be inserted into integer columns with explicitly specified length that's smaller than what the type can handle, e.g. 1234 can be inserted into an INT(2) column just fine. Thus, when calcualting the maximum width of expressions involving such restricted integer columns we need to use the implicit maximum width of the field instead of the explicitly speficied one. Fixed the server to use the implicit maximum in such cases and made sure the implicit maximum is addjusted the same way as the explicit one wrt signedness. Fixed several test case results (ctype_*.result, metadata.result and type_ranges.result) to reflect the extended column widths. Added a regression test case in distinct.test. Note : this is the behavior preserving fix that makes 5.5 behave as 5.1 and earlier. In the mysql trunk we'll add a insert time check for the explict maximum size.	15 years ago
Magnus Blåudd	f8e86f50e2	Bug#12384993 EXTRA/RPL_TEST/CHECK_TYPE.INC NEED SUPPORT FOR SPECIFIC ENGINE - add support for choosing the engine of test table(t1) with $engine_type - add primary key to the test table(t1) to support replication of BLOB/TEXT (also with ENGINE=ndb) - change the suppression since the warning printed to error log now says "Column 1"	15 years ago
Serge Kozlov	f978c103bb	automerge	15 years ago
Georgi Kodinov	2b9c0451f7	weave null merge mysql-5.1->mysql-5.5	15 years ago
Georgi Kodinov	ef2d701c00	weave merge mysql-5.0->mysql-5.1	15 years ago
Luis Soares	c9eef1d74a	BUG#12416700: RPL_SHOW_SLAVE_HOSTS FAILS SPORADICALLY (TIMEOUT IN WAIT_SHOW_CONDITION) There was a typo in the name of one of the parameters to the include file wait_show_condition. The parameter name was being set to "connection" instead of "condition". We fix this typo, improve one instruction in the test case and deploy parameter checks inside wait_show_condition.inc.	15 years ago
Serge Kozlov	4dde684315	automerge 5.1->5.5	15 years ago
Serge Kozlov	e8b54a7ce9	WL#5867 Replaced the error code by error name	15 years ago
Bjorn Munch	5a75bb9f11	WL #5680 MTR results written to file with well defined format Added --result-file option, which will produce var/mtr-results.txt Output has a simple format: <tag> : <value> for general info on test run { <tag> : <value> .... } for each test Output from failed tests are included but may be truncated. See WL for more details.	15 years ago
Alexander Nozdrin	75498ef924	Patch for Bug#12362125 (SP INOUT HANDLING IS BROKEN FOR TEXT TYPE). Attempts to assign value to a table column from trigger by using NEW.column_name pseudo-variable might result in garbled data. That happened when: - the column had a BLOB-based type (e.g. TEXT) and - the value being assigned was retrieved from stored routine variable of the same type. The problem was that BLOB values were not copied correctly in this case. Instead of doing a copy of a real value, the value's representation in record buffer was copied. This representation is essentially a pointer to a buffer associated with the virtual table for routine variables where the real value is stored. Since this buffer got freed once trigger was left or could have changed its contents when new value was assigned to corresponding routine variable such a shallow copying resulted in garbled data in NEW.colum_name column. It worked in 5.1 due to a subtle bug in create_virtual_tmp_table(): - in 5.1 create_virtual_tmp_table() returned a table which had db_low_byte_first == false. - in 5.5 and up create_virtual_tmp_table() returns a table which has db_low_byte_first == true. Actually, db_low_byte_first == false only for ISAM storage engine, which was deprecated and removed in 5.0. Having db_low_byte_first == false led to getting false in the complex condition for the 2nd "if" in field_conv(), which in turn led to copy-blob-behavior as a fall-back strategy: - to->table->s->db_low_byte_first was true (correct value) - from->table->s->db_low_byte_first was false (incorrect value) In 5.5 and up that condition is true, which means blob-values are not copied.	15 years ago
Alexander Nozdrin	cd501675d8	Patch for Bug#12374486 - SEVERE MEMORY LEAK IN PREPARED STATEMENTS THAT CALL STORED PROCEDURES. The bug was introduced by WL#4435. The problem was that if a stored procedure generated a few result sets with different set of columns, a new memory would be allocated after every EXECUTE for every result set. The fix is to introduce a new memory root in scope of MYSQL_STMT, and to store result-set metadata in that memory root.	15 years ago
Alexander Nozdrin	bc4095643b	Patch for Bug#11848763 / 60025 (SUBSTRING inside a stored function works too slow). The user-visible problem was that the server started to consume memory if a stored-routine of some sort is executed subsequently. The memory was freed only after the corresponding connection was closed. Technically, the problem was that the memory needed for temporary string conversions was allocated on the connection ("persistent") memory root, instead of statement one. The root cause of this problem was the incorrect patch for Bug 55744. That patch wrongly fixed a crash in prepared-statement-mode introduced by another patch. The patch for Bug 55744 used wrong condition to check if prepared statement mode is active (or whether the connection-scoped or statement-scoped memory root should be used). The thing is that for prepared statements such conversions should be done in the connection memory root, so that that the transformations of item-tree were correctly remembered in the PREPARE-phase. The fix is to use proper condition to detect prepared-statement-mode and use proper memory root.	15 years ago
Alexander Nozdrin	2593b14ccb	Preliminary patch for Bug#11848763 / 60025 (SUBSTRING inside a stored function works too slow). Background: - THD classes derives from Query_arena, thus inherits the 'state' attribute and related operations (is_stmt_prepare() & co). - Although these operations are available in THD, they must not be used. THD has its own attribute to point to the active Query_arena -- stmt_arena. - So, instead of using thd->is_stmt_prepare(), thd->stmt_arena->is_stmt_prepare() must be used. This was the root cause of Bug 60025. This patch enforces the proper way of calling those operations. is_stmt_prepare() & co are declared as private operations in THD (thus, they are hidden from being called on THD instance). The patch tries to minimize changes in 5.5.	15 years ago
Magnus Blåudd	b1ff2e6813	Add --with-debug=full support to BUILD/* scripts, this option has been lost between 5.1 and 5.5, it's purpose is to set the compiler flags in a way that does not optimize away the call stack(i.e don't use any -OX flags at all)	15 years ago
Magnus Blåudd	ec425cc5ac	Merge in patch for bug 12380149	15 years ago
Sunanda Menon	78e73ec219	Merge from mysql-5.0.93-release	15 years ago
bjorn.munch@oracle.com	f152d4cf05	Merge from mysql-5.5.12-release	15 years ago
Karen Langford	74afcca8f2	Merge from mysql-5.1.57-release	15 years ago
Luis Soares	f8b2499efe	BUG#12354268 Automerge from mysql-5.1 into mysql-5.5.	15 years ago
Luis Soares	8cc75b2d1e	BUG#12354268 Automerged bzr bundle from bug report: luis.soares@oracle.com-20110505224815-6ob90n7suxsoizvs.bundle	15 years ago
Luis Soares	6f3e97a6cb	BUG#11762616: BUG#55229: 'POSTION' Manual merge from mysql-5.1 into mysql-5.5. Conflicts ========= Text conflict in mysql-test/suite/rpl/t/rpl_row_until.test Text conflict in sql/handler.h Text conflict in storage/archive/ha_archive.cc	15 years ago

1 2 3 4 5 ...

69163 Commits (de91727eec494adc8d8dbee4a83fe8a6f1f93c39) All Branches Search

69163 Commits (de91727eec494adc8d8dbee4a83fe8a6f1f93c39)

All Branches