An error occurred fetching the project authors.
  1. 23 May, 2007 1 commit
    • dlenev@mockturtle.local's avatar
      5.0 version of fix for: · c07b3670
      dlenev@mockturtle.local authored
       Bug #23667 "CREATE TABLE LIKE is not isolated from alteration
                   by other connections"
       Bug #18950 "CREATE TABLE LIKE does not obtain LOCK_open"
      As well as:
       Bug #25578 "CREATE TABLE LIKE does not require any privileges
                   on source table".
      
      The first and the second bugs resulted in various errors and wrong
      binary log order when one tried to execute concurrently CREATE TABLE LIKE
      statement and DDL statements on source table or DML/DDL statements on its
      target table.
      
      The problem was caused by incomplete protection/table-locking against
      concurrent statements implemented in mysql_create_like_table() routine.
      We solve it by simply implementing such protection in proper way (see
      comment for sql_table.cc for details).
      
      The third bug allowed user who didn't have any privileges on table create
      its copy and therefore circumvent privilege check for SHOW CREATE TABLE.
      
      This patch solves this problem by adding privilege check, which was missing.
      
      Finally it also removes some duplicated code from mysql_create_like_table().
      
      Note that, altough tests covering concurrency-related aspects of CREATE TABLE
      LIKE behaviour will only be introduced in 5.1, they were run manually for
      this patch as well.
      c07b3670
  2. 30 Mar, 2007 1 commit
    • svoj@mysql.com/june.mysql.com's avatar
      BUG#26138 - REPAIR TABLE with option USE_FRM erases all records in · 556de62f
      svoj@mysql.com/june.mysql.com authored
                  ARCHIVE table
      ARCHIVE table was truncated by REPAIR TABLE ... USE_FRM statement.
      The table handler returned its file name extensions in a wrong order.
      REPAIR TABLE believed it has to use the meta file to create a new table
      from it.
      
      With the fixed order, REPAIR TABLE does now use the data file to create
      a new table. So REPAIR TABLE ... USE_FRM works well with ARCHIVE engine
      now.
      
      This issue affects 5.0 only, since in 5.1 ARCHIVE engine stores meta
      information and data in the same file.
      556de62f
  3. 31 Dec, 2006 1 commit
    • kent@mysql.com/kent-amd64.(none)'s avatar
      my_strtoll10-x86.s: · 6523aca7
      kent@mysql.com/kent-amd64.(none) authored
        Corrected spelling in copyright text
      Makefile.am:
        Don't update the files from BitKeeper
      Many files:
        Removed "MySQL Finland AB & TCX DataKonsult AB" from copyright header
        Adjusted year(s) in copyright header 
      Many files:
        Added GPL copyright text
      Removed files:
        Docs/Support/colspec-fix.pl
        Docs/Support/docbook-fixup.pl
        Docs/Support/docbook-prefix.pl
        Docs/Support/docbook-split
        Docs/Support/make-docbook
        Docs/Support/make-makefile
        Docs/Support/test-make-manual
        Docs/Support/test-make-manual-de
        Docs/Support/xwf
      6523aca7
  4. 23 Dec, 2006 1 commit
  5. 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
  6. 30 Aug, 2006 1 commit
  7. 10 Aug, 2006 1 commit
  8. 10 Jul, 2006 1 commit
  9. 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
  10. 04 Jul, 2006 1 commit
  11. 29 Jun, 2006 1 commit
  12. 02 Jun, 2006 1 commit
  13. 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
  14. 13 Apr, 2006 2 commits
  15. 12 Apr, 2006 1 commit
  16. 25 Feb, 2006 1 commit
  17. 17 Feb, 2006 1 commit
  18. 26 Nov, 2005 1 commit
  19. 10 Nov, 2005 1 commit
  20. 03 Nov, 2005 1 commit
  21. 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
  22. 10 Oct, 2005 1 commit
  23. 05 Oct, 2005 1 commit
  24. 04 Oct, 2005 1 commit
  25. 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
  26. 30 Sep, 2005 3 commits
  27. 22 Sep, 2005 1 commit
  28. 20 Sep, 2005 1 commit
  29. 19 Sep, 2005 1 commit
  30. 13 Sep, 2005 1 commit
  31. 30 Aug, 2005 1 commit
  32. 29 Aug, 2005 1 commit
  33. 17 Aug, 2005 1 commit
  34. 12 Aug, 2005 1 commit
  35. 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
  36. 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
  37. 17 Jun, 2005 1 commit