1. 15 Nov, 2016 1 commit
  2. 10 Nov, 2016 1 commit
    • Alexander Barkov's avatar
      A join patch for MDEV-10780 and MDEV-11265 · 1d9b043a
      Alexander Barkov authored
      MDEV-10780 Server crashes in in create_tmp_table
      MDEV-11265 Access defied when CREATE VIIEW v1 AS SELECT DEFAULT(column) FROM t1
      
      Item_default_value and Item_insert_value erroneously derive from Item_field
      but forgot to override some methods that apply only to true fields,
      so the server code mixes Item_{default|insert}_value instances with real
      table fields (i.e. true Item_field) in some cases.
      Overriding a few methods to avoid this.
      
      TODO: we should eventually derive Item_default_value (and Item_insert_value)
      directly from Item, as they don't really need the entire Item_field,
      Item_ident and Item_result_field functionality.
      Only the member "Field *field" related functionality is actually needed,
      like val_xxx(), is_null(), get_geometry_type(), charset_for_protocol(), etc.
      1d9b043a
  3. 04 Nov, 2016 1 commit
    • Kristian Nielsen's avatar
      MDEV-10863: parallel replication tries to continue from wrong position · 717f2128
      Kristian Nielsen authored
      This occured when the SQL thread (but not the IO thread) stops while
      GTID and parallel replication are used with multiple domain ids in the
      GTID position, and is restarted.
      
      In this case, the SQL needs to start some way back in the relay log,
      applying or skipping events within each replication domain as
      appropriate.
      
      The SQL threads starts at the beginning of an old relay log file, and
      this position may be in the middle of an event group. The bug was that
      such partial event group could be re-applied, causing replication
      corruption.
      
      This patch fixes the issue, by making sure to skip any initial events
      that were part of an earlier (already applied) event group.
      717f2128
  4. 01 Nov, 2016 1 commit
  5. 31 Oct, 2016 1 commit
  6. 28 Oct, 2016 2 commits
  7. 27 Oct, 2016 4 commits
  8. 26 Oct, 2016 9 commits
  9. 25 Oct, 2016 12 commits
  10. 23 Oct, 2016 1 commit
  11. 22 Oct, 2016 1 commit
    • Vladislav Vaintroub's avatar
      MDEV-11104 Fix client to correctly retrieve current user name on Windows · fb38d264
      Vladislav Vaintroub authored
      Prior to this patch name of the user was  read from environment variable
      USER, with a fallback to 'ODBC', if the environment variable is not set.
      
      The name of the env.variable is incorrect (USERNAME usually contains current
      user's name,  but not USER), which made client to  always determine
      current user as 'ODBC'.
      
      The fix is to use GetUserName() instead.
      fb38d264
  12. 21 Oct, 2016 3 commits
  13. 18 Oct, 2016 1 commit
  14. 17 Oct, 2016 2 commits