1. 24 Jan, 2008 1 commit
    • istruewing@stella.local's avatar
      Bug#29182 - MyISAMCHK reports wrong character set · 8aebd394
      istruewing@stella.local authored
      myisamchk did always show Character set: latin1_swedish_ci (8),
      regardless what DEFAULT CHARSET the table had.
      
      When the server created a MyISAM table, it did not copy the
      characterset number into the MyISAM create info structure.
      
      Added assignment of charset number to MI_CREATE_INFO.
      8aebd394
  2. 21 Jan, 2008 1 commit
  3. 19 Jan, 2008 1 commit
  4. 17 Jan, 2008 1 commit
    • acurtis/antony@xiphis.org/ltamd64.xiphis.org's avatar
      Bug#33067 · 7fe68882
        "Update of CSV row incorrect for some BLOBs"
        when reading in rows, move blob columns into temporary storage not
        allocated by Field_blob class or else row update operation will
        alter original row and make mysql think that nothing has been changed.
      fix incrementing wrong statistic values.
      7fe68882
  5. 16 Jan, 2008 4 commits
  6. 15 Jan, 2008 4 commits
  7. 14 Jan, 2008 1 commit
    • istruewing@stella.local's avatar
      Bug#33222 - myisam-table drops rows when column is added · f126800b
      istruewing@stella.local authored
                 and a char-field > 128 exists
      
      CHECK TABLE (non-QUICK) and any form of repair table did wrongly rate
      records as corrupted under the following conditions:
      1. The table has dynamic row format and
      2. it has a CHAR like column > 127 bytes (but not VARCHAR)
         (for multi-byte character sets this could be less than 127
         characters) and
      3. it has records with > 127 bytes significant length in that column
         (a byte beyond byte position 127 must be non-space).
      Affected were the statements CHECK TABLE, REPAIR TABLE, OPTIMIZE TABLE,
      ALTER TABLE. CHECK TABLE reported and marked the table as crashed if any
      record was present that fulfilled condition 3. The other statements
      deleted these records.
      
      The problem was a signed/unsigned compare in MyISAM code. A
      char to uchar change became necessary after the big byte to uchar
      change.
      f126800b
  8. 10 Jan, 2008 12 commits
  9. 09 Jan, 2008 5 commits
  10. 08 Jan, 2008 3 commits
  11. 07 Jan, 2008 1 commit
  12. 24 Dec, 2007 2 commits
  13. 21 Dec, 2007 4 commits