- 16 Aug, 2010 1 commit
-
-
Alexander Nozdrin authored
-
- 12 Aug, 2010 3 commits
-
-
Alexander Nozdrin authored
Fixing copyright text.
-
Alexander Nozdrin authored
-
Alexander Nozdrin authored
-
- 11 Aug, 2010 1 commit
-
-
Guilhem Bichot authored
it couldn't parse the --ssl option.
-
- 12 Aug, 2010 1 commit
-
-
Marc Alff authored
This is a performance improvement fix. Removed the "volatile" property of PFS_events_waits::m_wait_class. Simplified the code accordingly.
-
- 10 Aug, 2010 2 commits
-
-
Jonathan Perkin authored
-
Alfranio Correia authored
After BUG#36649, warnings for sub-statements are cleared when a new sub-statement is started. This is problematic since it suppresses warnings for unsafe statements in some cases. It is important that we always give a warning to the client, because the user needs to know when there is a risk that the slave goes out of sync. We fixed the problem by generating warning messages for unsafe statements while returning from a stored procedure, function, trigger or while executing a top level statement. We also started checking unsafeness when both performance and log tables are used. This is necessary after the performance schema which does a distinction between performance and log tables.
-
- 09 Aug, 2010 7 commits
-
-
Vladislav Vaintroub authored
Fix by adding "DEPENDS gen_lex_hash" to ADD_CUSTOM_COMMAND(), so it regenerates lex_hash.h whenever gen_lex_lash changes. Also, make sql dependent on GenServerSource to avoid concurrent generation of lex_hash.h (once for sql , and in parallel for embedded)
-
Alexander Nozdrin authored
-
Alexander Nozdrin authored
-
Jonathan Perkin authored
-
Jonathan Perkin authored
-
Davi Arnaut authored
-
Davi Arnaut authored
Post-merge fix: add missing comma.
-
- 06 Aug, 2010 1 commit
-
-
Davi Arnaut authored
Post-merge fix: remove --with-debug=full, it was only used for safemalloc.
-
- 05 Aug, 2010 5 commits
-
-
Bjorn Munch authored
-
Bjorn Munch authored
-
Davi Arnaut authored
Restore the original behavior of check-cpu with respect to core2. It isn't used as a actual target processor type, but as a mean to perform other kinds of architecture checks.
-
Vladislav Vaintroub authored
- Simplify sql-bench installation, do not try to resolve names : this leads to probem if builddir is symlink located on different filesystem. (reported by alik) - Make WITHOUT_XXX (disabling plugin) work for DEFAULT plugins. Prior to the patch is behaved just like MANDATORY. - LINK_LIBRARIES in MYSQL_ADD_PLUGIN had no effect for statically linked plugins. - Fix constant rebuild of initdb target on Windows.
-
Evgeny Potemkin authored
-
- 04 Aug, 2010 4 commits
-
-
Bjorn Munch authored
-
Alexander Nozdrin authored
-
Bjorn Munch authored
Follow-up patch: added test cases for -0 and while
-
Alexander Nozdrin authored
-
- 03 Aug, 2010 1 commit
-
-
Bjorn Munch authored
if() treated any non-numeric string as false Fixed to treat those as true instead Added some test cases Fixed missing $ in variable name in include/mix2.inc
-
- 02 Aug, 2010 3 commits
-
-
Evgeny Potemkin authored
A typo in the Item_cache_datetime::val_str caused an assertion to fail on the maximum time value.
-
Bjorn Munch authored
-
Bjorn Munch authored
The expect file can now include "restart:<server options>" Also drop check-testcase if this has been done Added comment explaining the restart: syntax
-
- 31 Jul, 2010 3 commits
-
-
Alexander Nozdrin authored
-
Alexander Nozdrin authored
-
Alexander Nozdrin authored
-
- 30 Jul, 2010 4 commits
-
-
Davi Arnaut authored
scripts if cmake is available. We need to always generate the scripts in order for the dual cmake/autotools support to work.
-
Alexander Nozdrin authored
-
Alexander Nozdrin authored
****** This patch fixes the following bugs: - Bug#5889: Exit handler for a warning doesn't hide the warning in trigger - Bug#9857: Stored procedures: handler for sqlwarning ignored - Bug#23032: Handlers declared in a SP do not handle warnings generated in sub-SP - Bug#36185: Incorrect precedence for warning and exception handlers The problem was in the way warnings/errors during stored routine execution were handled. Prior to this patch the logic was as follows: - when a warning/an error happens: if we're executing a stored routine, and there is a handler for that warning/error, remember the handler, ignore the warning/error and continue execution. - after a stored routine instruction is executed: check for a remembered handler and activate one (if any). This logic caused several problems: - if one instruction generates several warnings (errors) it's impossible to choose the right handler -- a handler for the first generated condition was chosen and remembered for activation. - mess with handling conditions in scopes different from the current one. - not putting generated warnings/errors into Warning Info (Diagnostic Area) is against The Standard. The patch changes the logic as follows: - Diagnostic Area is cleared on the beginning of each statement that either is able to generate warnings, or is able to work with tables. - at the end of a stored routine instruction, Diagnostic Area is left intact. - Diagnostic Area is checked after each stored routine instruction. If an instruction generates several condition, it's now possible to take a look at all of them and determine an appropriate handler.
-
Alexander Nozdrin authored
-
- 29 Jul, 2010 4 commits
-
-
Konstantin Osipov authored
-
Konstantin Osipov authored
-
Konstantin Osipov authored
-
Alexander Nozdrin authored
-