1. 20 Sep, 2006 1 commit
  2. 19 Sep, 2006 4 commits
  3. 18 Sep, 2006 2 commits
  4. 15 Sep, 2006 8 commits
  5. 14 Sep, 2006 1 commit
    • iggy@rolltop.ignatz42.dyndns.org's avatar
      Bug#21424 mysqldump failing to export/import views. ... · 4fa6c8c7
      iggy@rolltop.ignatz42.dyndns.org authored
      Bug#21424 mysqldump failing to export/import views.                                                                                                                                                                  
      
      Dumps are created for the tables in each specified database then for the views in each specified database. This bug occurs when any database's views depend on the mysql database's table data while being restored. 
      Added command line option --flush-privileges to the mysqldump utility which causes a FLUSH PRIVILIGES statement to be written to the dump after the mysql database.
      4fa6c8c7
  6. 12 Sep, 2006 3 commits
  7. 08 Sep, 2006 2 commits
  8. 07 Sep, 2006 5 commits
  9. 06 Sep, 2006 8 commits
  10. 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
  11. 04 Sep, 2006 5 commits