- 10 Sep, 2009 1 commit
-
-
Sergey Petrunya authored
-
- 09 Sep, 2009 2 commits
-
-
Sergey Petrunya authored
- Don't follow mainline on use of UNINIT_VAR yet, we haven't merged it in.
-
Sergey Petrunya authored
- Post-merge fixes
-
- 08 Sep, 2009 2 commits
-
-
Sergey Petrunya authored
-
Sergey Petrunya authored
-
- 07 Sep, 2009 1 commit
-
-
Sergey Petrunya authored
* Finished Monty and Jani's merge * Some InnoDB tests still fail (because it's old xtradb code run against newer testsuite). They are expected to go after mergning with the latest xtradb.
-
- 24 Aug, 2009 1 commit
-
-
Jonathan Perkin authored
- Add conditionals for bundled zlib and innodb plugin. - Apply patch from bug#46834 to install the test suite in RPMs. - Add plugins to RPMs. Disable example plugins.
-
- 21 Aug, 2009 1 commit
-
-
Joerg Bruehe authored
-
- 20 Aug, 2009 4 commits
-
-
Joerg Bruehe authored
-
Joerg Bruehe authored
-
Joerg Bruehe authored
-
Joerg Bruehe authored
This is a partial correction to the original fix for bug#37098 Get rid of "Installed (but unpackaged)" files in the RPM build which used a wrong variable. man/Makefile.am: Correction to the original fix: The variable to use is "$(mandir)", "$(manlibdir)" was wrong.
-
- 13 Aug, 2009 2 commits
-
-
Joerg Bruehe authored
This involves merge changesets and backports into QSP builds only, does not cause a contents change in 5.1
-
Joerg Bruehe authored
-
- 12 Aug, 2009 5 commits
-
-
Alexander Nozdrin authored
-
Alexander Nozdrin authored
-
Daniel Fischer authored
-
unknown authored
-
Sergey Vojtovich authored
not ready to run with innoplug-1.0.4.
-
- 11 Aug, 2009 11 commits
-
-
Joerg Bruehe authored
automerge didn't handle this correctly, so test "view" was corrected manually.
-
Davi Arnaut authored
-
Davi Arnaut authored
-
Joerg Bruehe authored
The test for the 45806 entry in our bug DB got applied twice, in different places for the "view.test" and "view.result" files. The fix is to simply remove the erroneous insertion.
-
Davi Arnaut authored
-
Vladislav Vaintroub authored
-
Vladislav Vaintroub authored
widely used, in replication (delete_allow_opened) and for named pipe support. We do not support Win9x anymore.
-
Davi Arnaut authored
-
Davi Arnaut authored
-
Sergey Vojtovich authored
-
unknown authored
-
- 10 Aug, 2009 5 commits
-
-
Davi Arnaut authored
-
Aleksandr Kuzminsky authored
-
unknown authored
-
Davi Arnaut authored
-
Martin Hansson authored
-
- 09 Aug, 2009 1 commit
-
-
Aleksandr Kuzminsky authored
-
- 08 Aug, 2009 1 commit
-
-
Davi Arnaut authored
The problem is that the lexer could inadvertently skip over the end of a query being parsed if it encountered a malformed multibyte character. A specially crated query string could cause the lexer to jump up to six bytes past the end of the query buffer. Another problem was that the laxer could use unfiltered user input as a signed array index for the parser maps (having upper and lower bounds 0 and 256 respectively). The solution is to ensure that the lexer only skips over well-formed multibyte characters and that the index value of the parser maps is always a unsigned value. mysql-test/r/ctype_recoding.result: Update test case result: ending backtick is not skipped over anymore. sql/sql_lex.cc: Characters being analyzed must be unsigned as they can be used as indexes for the parser maps. Only skip over if the string is a valid multi-byte sequence. tests/mysql_client_test.c: Add test case for Bug#45010
-
- 07 Aug, 2009 1 commit
-
-
Martin Hansson authored
Problem 1: When the 'Using index' optimization is used, the optimizer may still - after cost-based optimization - decide to use another index in order to avoid using a temporary table. But when this happens, the flag to the storage engine to read index only (not table) was still set. Fixed by resetting the flag in the storage engine and TABLE structure in the above scenario, unless the new index allows for the same optimization. Problem 2: When a 'ref' access method was employed by cost-based optimizer, (when the column is non-NULLable), it was assumed that it needed no initialization if 'quick' access methods (since they are based on range scan). When ORDER BY optimization overrides the decision, however, it expects to have this initialized and hence crashes. Fixed in 5.1 (was fixed in 6.0 already) by initializing 'quick' even when there's 'ref' access. mysql-test/r/order_by.result: Bug#46454: Test result. mysql-test/t/order_by.test: Bug#46454: Test case. sql/sql_select.cc: Bug#46454: Problem 1 fixed in make_join_select() Problem 2 fixed in test_if_skip_sort_order() sql/table.h: Bug#46454: Added comment to field.
-
- 06 Aug, 2009 2 commits
-
-
Ignacio Galarza authored
-
Ignacio Galarza authored
- Remove offensive quotes.
-