An error occurred fetching the project authors.
  1. 12 Sep, 2006 1 commit
    • svoj@april.(none)'s avatar
      BUG#20256 - LOCK WRITE - MyISAM · 44f167ee
      svoj@april.(none) authored
      Only MyISAM tables locked with LOCK TABLES ... WRITE were affected.
      
      A query that is optimized with index_merge doesn't reflect rows
      inserted within LOCK TABLES.
      
      MyISAM doesn't flush a state within LOCK TABLES. index_merge
      optimization creates a copy of the handler, which thus gets
      outdated MyISAM state.
      
      New handler->clone() method is introduced to fix this problem.
      For non-MyISAM storage engines it allocates a handler and opens
      it with ha_open(). For MyISAM it additionally copies MyISAM state
      pointer to cloned handler.
      44f167ee
  2. 10 Jul, 2006 1 commit
  3. 05 Jul, 2006 1 commit
    • guilhem@mysql.com's avatar
      Fix for BUG#20188 "REPLACE or ON DUPLICATE KEY UPDATE in · a43c4b02
      guilhem@mysql.com authored
      auto_increment breaks binlog":
      if slave's table had a higher auto_increment counter than master's (even
      though all rows of the two tables were identical), then in some cases,
      REPLACE and INSERT ON DUPLICATE KEY UPDATE failed to replicate
      statement-based (it inserted different values on slave from on master).
      write_record() contained a "thd->next_insert_id=0" to force an adjustment
      of thd->next_insert_id after the update or replacement. But it is this
      assigment introduced indeterminism of the statement on the slave, thus
      the bug. For ON DUPLICATE, we replace that assignment by a call to
      handler::adjust_next_insert_id_after_explicit_value() which is deterministic
      (does not depend on slave table's autoinc counter). For REPLACE, this
      assignment can simply be removed (as REPLACE can't insert a number larger
      than thd->next_insert_id).
      We also move a too early restore_auto_increment() down to when we really know
      that we can restore the value.
      a43c4b02
  4. 04 Jul, 2006 1 commit
  5. 29 Jun, 2006 1 commit
  6. 02 Jun, 2006 1 commit
  7. 09 May, 2006 1 commit
    • acurtis@xiphis.org's avatar
      bug#10952 · 47e89f20
      acurtis@xiphis.org authored
        "alter table from MyISAM to MERGE lost data without errors and warnings"
        Add new handlerton flag which prevent user from altering table storage
        engine to storage engines which would lose data. Both 'blackhole' and 
        'merge' are marked with the new flag.
        Tests included.
      47e89f20
  8. 13 Apr, 2006 2 commits
  9. 12 Apr, 2006 1 commit
  10. 25 Feb, 2006 1 commit
  11. 17 Feb, 2006 1 commit
  12. 26 Nov, 2005 1 commit
  13. 10 Nov, 2005 1 commit
  14. 03 Nov, 2005 1 commit
  15. 02 Nov, 2005 1 commit
    • igor@rurik.mysql.com's avatar
      #view.test#: · fddc99bc
      igor@rurik.mysql.com authored
        new file
      sql_table.cc, handler.h:
        Fixed bug #14540.
        Added error mnemonic code HA_ADMIN_NOT_BASE_TABLE
        to report that an operation cannot be applied for views.
      view.test, view.result:
        Added a test case for bug #14540.
      errmsg.txt:
        Fixed bug #14540.
        Added error ER_CHECK_NOT_BASE_TABLE.
      fddc99bc
  16. 10 Oct, 2005 1 commit
  17. 05 Oct, 2005 1 commit
  18. 04 Oct, 2005 1 commit
  19. 03 Oct, 2005 1 commit
    • brian@zim.(none)'s avatar
      Next big patch for loadable storage engines! · 54a95899
      brian@zim.(none) authored
      Handlerton array is now created instead of using sys_table_types_st. All storage engines can now have inits and giant ifdef's are now gone for startup. No compeltely clean yet, handlertons will next be merged with sys_table_types. Federated and archive now have real cleanup if their inits fail. 
      54a95899
  20. 30 Sep, 2005 3 commits
  21. 22 Sep, 2005 1 commit
  22. 20 Sep, 2005 1 commit
  23. 19 Sep, 2005 1 commit
  24. 13 Sep, 2005 1 commit
  25. 30 Aug, 2005 1 commit
  26. 29 Aug, 2005 1 commit
  27. 17 Aug, 2005 1 commit
  28. 12 Aug, 2005 1 commit
  29. 20 Jul, 2005 1 commit
    • konstantin@mysql.com's avatar
      Implement MySQL framework to support consistent read views in · 21957c42
      konstantin@mysql.com authored
      cursors. This should fix Bug#11813 when InnoDB part is in 
      (tested with a draft patch).
      The idea of the patch is that if a storage engine supports
      consistent read views, we open one when open a cursor,
      set is as the active view when fetch from the cursor, and close
      together with cursor close.
      21957c42
  30. 19 Jul, 2005 1 commit
    • konstantin@mysql.com's avatar
      A fix and a test case for Bug#10760 and complementary cleanups. · 14344b65
      konstantin@mysql.com authored
      The idea of the patch
      is that every cursor gets its own lock id for table level locking.
      Thus cursors are protected from updates performed within the same 
      connection. Additionally a list of transient (must be closed at
      commit) cursors is maintained and all transient cursors are closed
      when necessary. Lastly, this patch adds support for deadlock
      timeouts to TLL locking when using cursors.
      + post-review fixes.
      14344b65
  31. 17 Jun, 2005 1 commit
  32. 08 Jun, 2005 1 commit
    • msvensson@neptunus.(none)'s avatar
      BUG#10365 Cluster handler uses non-standard error codes · 8771c732
      msvensson@neptunus.(none) authored
       - Added better error messages when trying to open a table that can't be discovered or unpacked. The most likely cause of this is that it does not have any frm data, probably since it has been created from NdbApi or is a NDB system table.
       - Separated functionality that was in ha_create_table_from_engine into two functions. One that checks if the table exists and another one that tries to create the table from the engine.
      8771c732
  33. 18 May, 2005 2 commits
  34. 13 May, 2005 1 commit
  35. 04 May, 2005 1 commit
  36. 20 Apr, 2005 1 commit
    • heikki@hundin.mysql.fi's avatar
      Many files: · 8974ce08
      heikki@hundin.mysql.fi authored
        Semi-synchronous replication for InnoDB type tables; before telling the client that a commit has been processed, wait that the replication thread has returned from my_net_send() where it sends the binlog to the slave; note that TCP/IP, even with the TCP_NODELAY option does not guarantee that the slave has RECEIVED the data - this is just heuristic at the moment; this is useful in failover: in almost all cases, every transaction that has returned from the commit has been sent and processed in the slave, which makes failover to the slave simpler if the master crashes; the code does not work yet as is, because MySQL should call innobase_report_binlog_offset_and_commit() in a commit; we will most probably return that call to 5.0.x, to make InnoDB Hot Backup and group commit to work again; XA code broke them temporarily in 5.0.3
      8974ce08