1. 06 Oct, 2016 1 commit
  2. 04 Oct, 2016 7 commits
    • Monty's avatar
      After merge and bug fixes · 14b1c8c8
      Monty authored
      - Fixed compiler warnings
      - Removed have_debug.inc from innochecksum_3
      - Fixed race condition in innodb_buffer_pool_load
      - Fixed merge issue in innodb-bad-key-change.test
      - Fixed missing array allocation that could cause
        function_defaults_notembedded to fail
      - Fixed thread_cache_size_func
      14b1c8c8
    • Monty's avatar
      Remove end . from error messages to get them consistent · af7490f9
      Monty authored
      Fixed a few failing tests
      af7490f9
    • Monty's avatar
      Fixed compiler warnings and failing tests · c1125c32
      Monty authored
      c1125c32
    • Monty's avatar
      Use sql_mode_t for sql_mode. · 7b96416f
      Monty authored
      This fixed several cases where we where using just ulong for sql_mode
      7b96416f
    • Monty's avatar
      MDEV-6112 multiple triggers per table · 8be53a38
      Monty authored
      This is similar to MysQL Worklog 3253, but with
      a different implementation. The disk format and
      SQL syntax is identical with MySQL 5.7.
      
      Fetures supported:
      - "Any" ammount of any trigger
      - Supports FOLLOWS and PRECEDES to be
        able to put triggers in a certain execution order.
      
      Implementation details:
      - Class Trigger added to hold information about a trigger.
        Before this trigger information was stored in a set of lists in
        Table_triggers_list and in Table_triggers_list::bodies
      - Each Trigger has a next field that poinst to the next Trigger with the
        same action and time.
      - When accessing a trigger, we now always access all linked triggers
      - The list are now only used to load and save trigger files.
      - MySQL trigger test case (trigger_wl3253) added and we execute these
        identically.
      - Even more gracefully handling of wrong trigger files than before. This
        is useful if a trigger file uses functions or syntax not provided by
        the server.
      - Each trigger now has a "Created" field that shows when the trigger was
        created, with 2 decimals.
      
      Other comments:
      - Many of the changes in test files was done because of the new "Created"
        field in the trigger file. This shows up in SHOW ... TRIGGER and when
        using information_schema.trigger.
      - Don't check if all memory is released if on uses --gdb;  This is needed
        to be able to get a list from safemalloc of not freed memory while
        debugging.
      - Added option to trim_whitespace() to know how many prefix characters
        was skipped.
      - Changed a few ulonglong sql_mode to sql_mode_t, to find some wrong usage
        of sql_mode.
      8be53a38
    • Sergei Golubchik's avatar
      simplify the ipv6 check · 0bae1957
      Sergei Golubchik authored
      0bae1957
    • Daniel Black's avatar
      70dcb46e
  3. 03 Oct, 2016 5 commits
  4. 01 Oct, 2016 5 commits
  5. 30 Sep, 2016 2 commits
  6. 29 Sep, 2016 1 commit
  7. 27 Sep, 2016 1 commit
  8. 26 Sep, 2016 2 commits
    • Igor Babaev's avatar
      Fixed bug mdev-10889 · b91bd822
      Igor Babaev authored
      The bug was in the code of the recursive method
      With_element::check_unrestricted_recursive. For recursive
      calls of this method sel->get_with_element()->owner != owner.
      b91bd822
    • Igor Babaev's avatar
      Fixed bug mdev-10884. · 1f1990a1
      Igor Babaev authored
      If a materialized derived table / view is specified by a unit
      with SELECTs containing ORDER BY ... LIMIT then condition pushdown
      cannot be done for these SELECTs.
      If a materialized derived table / view is specified by a unit
      containing global ORDER BY ... LIMIT then condition pushdown
      cannot be done for this unit.
      1f1990a1
  9. 25 Sep, 2016 4 commits
  10. 24 Sep, 2016 12 commits