An error occurred fetching the project authors.
  1. 14 Mar, 2008 1 commit
    • svoj@mysql.com/june.mysql.com's avatar
      BUG#28248 - mysqldump results with MERGE ... UNION=() cannot be executed · 1f0e9f5a
      svoj@mysql.com/june.mysql.com authored
      When there are no underlying tables specified for a merge table,
      SHOW CREATE TABLE outputs a statement that cannot be executed. The
      same is true for mysqldump (it generates dumps that cannot be
      executed).
      
      This happens because SQL parser does not accept empty UNION() clause.
      
      This patch changes the following:
      - it is now possible to execute CREATE/ALTER statement with
        empty UNION() clause.
      - the same as above, but still worth noting: it is now possible to
        remove underlying tables mapping using ALTER TABLE ... UNION=().
      - SHOW CREATE TABLE does not output UNION() clause if there are
        no underlying tables specified for a merge table. This makes
        mysqldump slightly smaller.
      1f0e9f5a
  2. 12 Dec, 2007 1 commit
  3. 26 Nov, 2007 1 commit
    • kaa@polly.(none)'s avatar
      Fix for bug #28837: MyISAM storage engine error (134) doing delete with · 8fdd9087
      kaa@polly.(none) authored
      self-join
      
      When doing DELETE with self-join on a MyISAM or MERGE table, it could
      happen that a record being retrieved in join_read_next_same() has
      already been deleted by previous iterations. That caused the engine's
      index_next_same() method to fail with HA_ERR_RECORD_DELETED error and
      the whole DELETE query to be aborted with an error.
      
      Fixed by suppressing the HA_ERR_RECORD_DELETED error in
      hy_myisam::index_next_same() and ha_myisammrg::index_next_same(). Since
      HA_ERR_RECORD_DELETED can only be returned by MyISAM, there is no point
      in filtering this error in the SQL layer.
      8fdd9087
  4. 09 Oct, 2007 1 commit
  5. 05 Jun, 2007 1 commit
    • svoj@mysql.com/april.(none)'s avatar
      BUG#26976 - Missing table in merge not noted in related error msg + · bd8f81f4
      svoj@mysql.com/april.(none) authored
                  SHOW CREATE TABLE fails
      
      Underlying table names, that merge engine fails to open were not
      reported.
      
      With this fix CHECK TABLE issued against merge table reports all
      underlying table names that it fails to open. Other statements
      are unaffected, that is underlying table names are not included
      into error message.
      
      This fix doesn't solve SHOW CREATE TABLE issue.
      bd8f81f4
  6. 10 Apr, 2007 1 commit
    • svoj@mysql.com/april.(none)'s avatar
      BUG#24342 - Incorrect results with query over MERGE table · bcbcacb8
      svoj@mysql.com/april.(none) authored
      MERGE engine may return incorrect values when several representations
      of equal keys are present in the index. For example "groß" and "gross"
      or "gross" and "gross " (trailing space), which are considered equal,
      but have different lengths.
      
      The problem was that key length was not recalculated after key lookup.
      
      Only MERGE engine is affected.
      bcbcacb8
  7. 20 Mar, 2007 1 commit
  8. 13 Mar, 2007 1 commit
    • svoj@mysql.com/april.(none)'s avatar
      BUG#26881 - Large MERGE tables report incorrect specification when no · cb132bea
      svoj@mysql.com/april.(none) authored
                  differences in tables
      Certain merge tables were wrongly reported as having incorrect definition:
      - Some fields that are 1 byte long (e.g. TINYINT, CHAR(1)), might
        be internally casted (in certain cases) to a different type on a
        storage engine layer. (affects 4.1 and up)
      - If tables in a merge (and a MERGE table itself) had short VARCHAR column (less
        than 4 bytes) and at least one (but not all) tables were ALTER'ed (even to an
        identical table: ALTER TABLE xxx ENGINE=yyy), table definitions went ouf of
        sync. (affects 4.1 only)
      
      This is fixed by relaxing a check for underlying conformance and setting
      field type to FIELD_TYPE_STRING in case varchar is shorter than 4
      when a table is created.
      cb132bea
  9. 05 Mar, 2007 1 commit
    • istruewing@chilla.local's avatar
      Bug#26464 - insert delayed + update + merge = corruption · 629fed6c
      istruewing@chilla.local authored
      Using INSERT DELAYED on MERGE tables could lead to table
      corruptions.
      
      The manual lists a couple of storage engines, which can be
      used with INSERT DELAYED. MERGE is not in this list.
      
      The attempt to try it anyway has not been rejected yet.
      This bug was not detected earlier as it can work under
      special circumstances. Most notable is low concurrency.
      
      To be safe, this patch rejects any attempt to use INSERT
      DELAYED on MERGE tables.
      629fed6c
  10. 31 Jan, 2007 1 commit
  11. 28 Sep, 2006 1 commit
  12. 19 Sep, 2006 1 commit
  13. 12 Jul, 2006 1 commit
  14. 10 Jul, 2006 1 commit
  15. 31 May, 2006 1 commit
    • acurtis@xiphis.org's avatar
      Bug#19648 · 0cd7ac83
      acurtis@xiphis.org authored
        "Merge table does not work with bit types"
         MERGE should have HA_CAN_BIT_FIELD feature bit set or else table row is
         formatted incorrectly.
      0cd7ac83
  16. 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
  17. 20 Dec, 2005 1 commit
    • ingo@mysql.com's avatar
      BUG#5390 - problems with merge tables · b0e84cb9
      ingo@mysql.com authored
      Problem #1: INSERT...SELECT, Version for 5.0.
      Extended the unique table check by a check of lock data.
      Merge sub-tables cannot be detected by doing name checks only.
      b0e84cb9
  18. 07 Dec, 2005 1 commit
    • ingo@mysql.com's avatar
      BUG#5390 - problems with merge tables · 5aa315e2
      ingo@mysql.com authored
      Problem #1: INSERT...SELECT, Version for 4.1.
      INSERT ... SELECT with the same table on both sides (hidden
      below a MERGE table) does now work by buffering the select result.
      The duplicate detection works now after open_and_lock_tables() 
      on the locks.
      I did not find a test case that failed without the change in
      sql_update.cc. I made the change anyway as it should in theory
      fix a possible MERGE table problem with multi-table update.
      5aa315e2
  19. 29 Nov, 2005 1 commit
    • ingo@mysql.com's avatar
      BUG#5390 - problems with merge tables · 76861ac6
      ingo@mysql.com authored
      Problem #1: INSERT...SELECT
      INSERT ... SELECT with the same table on both sides (hidden
      below a MERGE table) does now work by buffering the select result.
      The duplicate detection works now after open_and_lock_tables() 
      on the locks.
      I did not find a test case that failed without the change in
      sql_update.cc. I made the change anyway as it should in theory
      fix a possible MERGE table problem with multi-table update.
      76861ac6
  20. 29 Sep, 2005 1 commit
  21. 27 Sep, 2005 1 commit
  22. 23 Sep, 2005 2 commits
  23. 28 Jul, 2005 1 commit
  24. 18 May, 2005 1 commit
  25. 27 Dec, 2004 1 commit
  26. 23 Dec, 2004 1 commit
    • ingo@mysql.com's avatar
      WL#1895 - Print message to error log in case of detected MyISAM corruption · c39be2d0
      ingo@mysql.com authored
      Changed my_error() to print error messages, which come from
      arbitrary registered ranges of error messages. Messages can
      be unregistered (and should be at end of the program).
      Added registration of handler error messages.
      Added a new mi_print_error() macro and a new 
      mi_report_error() function, which supply error
      messages with a table name.
      Added calls to mi_print_error() or mi_report_error()
      at all places in MyISAM, where table corruption is detected.
      c39be2d0
  27. 29 Nov, 2004 1 commit
  28. 09 Sep, 2004 1 commit
  29. 27 Aug, 2004 1 commit
  30. 25 Jun, 2004 1 commit
  31. 04 Mar, 2004 1 commit
  32. 10 Dec, 2003 1 commit
  33. 03 Jul, 2003 1 commit
  34. 01 Jul, 2003 1 commit
  35. 27 Jun, 2003 1 commit
  36. 16 Jan, 2003 1 commit
  37. 05 Jan, 2003 1 commit
  38. 14 Dec, 2002 1 commit
    • monty@mashka.mysql.fi's avatar
      Fixes for binary protocol (complement to last push) · d49167ba
      monty@mashka.mysql.fi authored
      Changed timestamp to return string in YYYY-MM-DD HH:MM:SS format.
      DATE_ADD() and related functions now returns correct DATE/DATETIME type depending on argument types.
      Now all tests passes, still some work left to remove warnings in log files from mysql-test-run
      d49167ba
  39. 17 Nov, 2002 1 commit