An error occurred fetching the project authors.
  1. 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
  2. 20 Mar, 2007 1 commit
  3. 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
  4. 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
  5. 31 Jan, 2007 1 commit
  6. 22 Jan, 2007 1 commit
  7. 28 Sep, 2006 2 commits
  8. 19 Sep, 2006 1 commit
  9. 12 Jul, 2006 1 commit
  10. 10 Jul, 2006 1 commit
  11. 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
  12. 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
  13. 22 Dec, 2005 1 commit
    • ingo@mysql.com's avatar
      BUG#5390 - problems with merge tables · a04c5adb
      ingo@mysql.com authored
      Problem #1: INSERT...SELECT, Version for 5.1.
      Extended the unique table check by a check of lock data.
      Merge sub-tables cannot be detected by doing name checks only.
      a04c5adb
  14. 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
  15. 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
  16. 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
  17. 23 Nov, 2005 1 commit
    • monty@mysql.com's avatar
      Table definition cache, part 2 · e42c9809
      monty@mysql.com authored
      The table opening process now works the following way:
      - Create common TABLE_SHARE object
      - Read the .frm file and unpack it into the TABLE_SHARE object
      - Create a TABLE object based on the information in the TABLE_SHARE
        object and open a handler to the table object
      
      Other noteworthy changes:
      - In TABLE_SHARE the most common strings are now LEX_STRING's
      - Better error message when table is not found
      - Variable table_cache is now renamed 'table_open_cache'
      - New variable 'table_definition_cache' that is the number of table defintions that will be cached
      - strxnmov() calls are now fixed to avoid overflows
      - strxnmov() will now always add one end \0 to result
      - engine objects are now created with a TABLE_SHARE object instead of a TABLE object.
      - After creating a field object one must call field->init(table) before using it
      
      - For a busy system this change will give you:
       - Less memory usage for table object
       - Faster opening of tables (if it's has been in use or is in table definition cache)
       - Allow you to cache many table definitions objects
       - Faster drop of table
      e42c9809
  18. 29 Sep, 2005 1 commit
  19. 27 Sep, 2005 1 commit
  20. 23 Sep, 2005 2 commits
  21. 28 Jul, 2005 1 commit
  22. 18 May, 2005 1 commit
  23. 27 Dec, 2004 1 commit
  24. 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
  25. 29 Nov, 2004 1 commit
  26. 09 Sep, 2004 1 commit
  27. 27 Aug, 2004 1 commit
  28. 25 Jun, 2004 1 commit
  29. 04 Mar, 2004 1 commit
  30. 10 Dec, 2003 1 commit
  31. 03 Jul, 2003 1 commit
  32. 01 Jul, 2003 1 commit
  33. 27 Jun, 2003 1 commit
  34. 16 Jan, 2003 1 commit
  35. 05 Jan, 2003 1 commit
  36. 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
  37. 17 Nov, 2002 1 commit
  38. 04 Nov, 2002 1 commit