1. 20 Sep, 2006 1 commit
  2. 19 Sep, 2006 1 commit
    • Kristofer.Pettersson@naruto.'s avatar
      Bug#20789 Merge Subtable Rename Causes Crash · 70316e06
      Kristofer.Pettersson@naruto. authored
      - When a MyISAM table which belongs to a merge table union and is 
        renamed the associated file descriptors are closed on windows.
        This causes a server crash next time an insert or update is 
        performed on the merge table.
      - This patch prevents the system from crashing on windows by
        checking for bad file descriptors every time the MyISAM table
        is locked by associated the merge table.
      70316e06
  3. 17 Sep, 2006 1 commit
  4. 14 Sep, 2006 1 commit
  5. 12 Sep, 2006 4 commits
  6. 08 Sep, 2006 2 commits
  7. 07 Sep, 2006 5 commits
  8. 06 Sep, 2006 8 commits
  9. 05 Sep, 2006 1 commit
    • guilhem@gbichot3.local's avatar
      Fix for BUG#11151 "LOAD DATA INFILE commits transaction in 5.0". · e4d3595b
      guilhem@gbichot3.local authored
      In 5.0 we made LOAD DATA INFILE autocommit in all engines, while
      only NDB wanted that. Users and trainers complained that it affected
      InnoDB and was a change compared to 4.1 where only NDB autocommitted.
      To revert to the behaviour of 4.1, we move the autocommit logic out of mysql_load() into
      ha_ndbcluster::external_lock().
      The result is that LOAD DATA INFILE commits all uncommitted changes
      of NDB if this is an NDB table, its own changes if this is an NDB
      table, but does not affect other engines.
      Note: even though there is no "commit the full transaction at end"
      anymore, LOAD DATA INFILE stays disabled in routines (re-entrency
      problems per a comment of Pem).
      Note: ha_ndbcluster::has_transactions() does not give reliable results
      because it says "yes" even if transactions are disabled in this engine...
      e4d3595b
  10. 04 Sep, 2006 11 commits
  11. 03 Sep, 2006 1 commit
  12. 02 Sep, 2006 4 commits