- 04 Feb, 2009 14 commits
-
-
Matthias Leich authored
-
Matthias Leich authored
-
Sergey Vojtovich authored
-
Matthias Leich authored
-
Magnus Svensson authored
-
Matthias Leich authored
-
Staale Smedseng authored
-
Sergey Vojtovich authored
Accessing well defined MERGE table may return an error stating that the merge table is incorrectly defined. This happens if MERGE child tables were accessed before and we failed to open another incorrectly defined MERGE table in this connection. myrg_open() internally used my_errno as a variable for determining failure, and thus could be tricked into a wrong decision by other uses of my_errno. With this fix we use function local boolean flag instead of my_errno to determine failure.
-
Sergey Glukhov authored
Problem: RelativeLocationPath can appear only after a node-set expression in the third and the fourth branches of this rule: PathExpr :: = LocationPath | FilterExpr | FilterExpr '/' RelativeLocationPath | FilterExpr '//' RelativeLocationPath XPatch code didn't check the type of FilterExpr and crashed. Fix: If FilterExpr is a scalar expression (variable reference, literal, number, scalar function call) return error.
-
Davi Arnaut authored
-
Andrei Elkin authored
fixing build issue, caused by the previous push.
-
Matthias Leich authored
-
Andrei Elkin authored
The bug happened because filtering-out a STMT_END_F-flagged event so that the transaction COMMIT finds traces of incomplete statement commit. Such situation is only possible with ndb circular replication. The filtered-out rows event is one that immediately preceeds the COMMIT query event. Fixed with deploying an the rows-log-event statement commit at executing of the transaction COMMIT event. Resources that were allocated by other than STMT_END_F-flagged event of the last statement are clean up prior execution of the commit logics.
-
Magnus Svensson authored
- Properly set --bindir=$path_client_bindir and --basedir=$basedir by adding %s format specifier
-
- 03 Feb, 2009 3 commits
-
-
Davi Arnaut authored
upgrading lock, even with low_priority_updates The problem is that there is no mechanism to control whether a delayed insert takes a high or low priority lock on a table. The solution is to modify the delayed insert thread ("handler") to take into account the global value of low_priority_updates when taking table locks. The value of low_priority_updates is retrieved when the insert delayed thread is created and will remain the same for the duration of the thread.
-
Matthias Leich authored
+ fix wrong resultfile have_outfile.require
-
Staale Smedseng authored
Option opt_threads is deprecated in 5.1, and a warning is printed when used. Will remove in 6.0.
-
- 02 Feb, 2009 16 commits
-
-
Patrick Crews authored
-
Patrick Crews authored
The original symptoms of this bug have been fixed as a consequence of other bug fixes. Taking this time to correct some formatting, such as replacing error numbers with names. Beginning this with 5.0
-
Serge Kozlov authored
The patch adds restart of mysql server and replacing of binlog file when mysql server is stopped.
-
Matthias Leich authored
- If missing: add "disconnect <session>" - If physical disconnect of non "default" sessions is not finished at test end: add routine which waits till this happened + additional improvements like - remove superfluous files created by the test - replace error numbers by error names - remove trailing spaces, replace tabs by spaces - unify writing of bugs within comments - correct comments - minor changes of formatting Modifications according to the code review are included. Fixed tests: grant2 grant3 lock_tables_lost_commit mysqldump openssl_1 outfile
-
Andrei Elkin authored
There are two issues: 1. 6.0 uses the obsolate master-*** server options; 2. the test is not deterministic in that although master vs slave consistency is fine, two runs of the test can have different results. The reason of the non-determinism is the combination of a chosen way to demo results and the ndb_autoincrement_prefetch_sz feature. The current patch fixes the 2nd issue by putting out results via diff_table macro instead of the former run-sensitive method. The 1st issue is going to be fixed by a separate patch to 6.0.
-
Tatiana A. Nurnberg authored
-
Alexander Barkov authored
Problem: Custom UCA collations didn't set the MY_CS_STRNXFRM flag, which resulted in "prefix_search" method instead of the required "seq_search". Problem2: (not metioned in the bug report) Custom UCA collations didn't also set the MY_CS_UNICODE flag, so an attempt to compare a column with a custom UCA collation to another column with a non-Unicode character set led to the "illegal mix of collation" error. Fix: the two missing flags was added into collation initialization. Upgrade: - All fulltext indexes with custom UCA collations should be rebuilt. - Non-fulltext custom UCA indexes should likely be rebuild as well.
-
Tatiana A. Nurnberg authored
-
Serge Kozlov authored
-
Serge Kozlov authored
Remove size of binlog file from SHOW BINARY LOGS. Changing size of binlog file is an affect of adding or removing events to/from binlog and it can be checked in next command of test: SHOW BINLOG EVENTS. For SHOW BINARY LOGS statement enough to show the list of file names.
-
Georgi Kodinov authored
fixed federated warnings
-
Sergey Glukhov authored
-
Bjorn Munch authored
-
Sergey Glukhov authored
-
Bjorn Munch authored
Changed [ skip ] to [ skipped ] and removed optional .
-
Georgi Kodinov authored
-
- 01 Feb, 2009 7 commits
-
-
Alfranio Correia authored
-
Alfranio Correia authored
-
Alfranio Correia authored
-
Luis Soares authored
-
Alfranio Correia authored
1 - MASTER_MYSOCK fixed inexistent environment variable. 2 - Fixed mismatch in result files due to changes in MTR.
-
Georgi Kodinov authored
-
Luis Soares authored
It seems that the length of the thick line printed by mtr when printing the suite name differs from mtr1 and mtr2, affecting the mtr filtering by PB2. This patch addresses it by restoring the thick line length to 78 (original length) instead of 60 (the one in mtr2).
-