1. 16 Feb, 2009 3 commits
  2. 15 Feb, 2009 3 commits
  3. 14 Feb, 2009 12 commits
  4. 13 Feb, 2009 15 commits
  5. 12 Feb, 2009 7 commits
    • Davi Arnaut's avatar
      Backport from 6.0 fix for Bug#38249 · 8865766a
      Davi Arnaut authored
      2722 Konstantin Osipov	2008-10-03
      Fix Bug#38249 innodb_log_arch_dir still in support files
      Remove a non-supported variable from cnf file templates.
      8865766a
    • Magnus Svensson's avatar
      Bug#42797 mtr.pl - temporary directory are deleted when child exit's · be5cc29e
      Magnus Svensson authored
      - Since we are only using the auto cleanup in one place of mtr.pl today, disable the
      autocleanup and write our own END handler that clean up the tmpdir only when the process
      that created it exits.
      be5cc29e
    • Georgi Kodinov's avatar
      cc5809f0
    • Georgi Kodinov's avatar
      merged 5.0-bugteam to a working tree · 47c53135
      Georgi Kodinov authored
      47c53135
    • Georgi Kodinov's avatar
      Bug #33813: Schema names are case-sensitive in DROP FUNCTION · 1c5fa3b6
      Georgi Kodinov authored
            
      Additional fix:
       1. Revert the unification of DROP FUNCTION
      and DROP PROCEDURE, because DROP FUNCTION can be used to
      drop UDFs (that have a non-qualified name and don't require
      database name to be present and valid).
       2. Fixed the case sensitivity problem by adding a call to 
      check_db_name() (similar to the sp_name production).
      1c5fa3b6
    • Sergey Vojtovich's avatar
      984c2489
    • V Narayanan's avatar
      Bug#40675 MySQL 5.1 crash with index merge algorithm and Merge tables · e80537b7
      V Narayanan authored
                  
      A Query in the MyISAM merge table was crashing 
      if the index merge algorithm was being used
      
      Index Merge optimization requires the reading of 
      multiple indexes at the same time. Reading multiple 
      indexes at once with current SE API means that we 
      need to have handler instance for each to-be-read 
      index. This is done by creating clones of the handlers 
      instances. The clone internally does a open of the handler.
      
      The open for a MERGE engine is handled in the following 
      phases
      
      1) open parent table
      2) generate list of underlying
         table
      3) attach underlying tables
      
      But the current implementation does only the first 
      phase (i.e.) open parent table.
      
      The current patch fixes this at the MERGE engine level, 
      by handling the clone operation within the MERGE engine 
      rather than in the storage engine API. It opens and 
      attaches the MyISAM tables on the MyISAM storage engine 
      interface directly within the MERGE engine. The new MyISAM 
      table instances, as well as the MERGE clone itself, are not 
      visible in the table cache. This is not a problem because
      all locking is handled by the original MERGE table from which
      this is cloned of.
      
      mysql-test/r/merge.result:
        updated the result file to reflect the new tests
        added to test the fix
      mysql-test/t/merge.test:
        Added new tests to verify that the index merge
        algorithm does not crash in the merge engine.
      storage/myisammrg/ha_myisammrg.cc:
        Implement the clone method, that handles
        
        1) Cloning the handler
        2) Opening underlying MYISAM child tables
        3) Copies the state of the original handler and the children
           into the cloned instances
        4) Sets the appropriate flags
      storage/myisammrg/ha_myisammrg.h:
        Added a flag that is set to indicate that the current 
        instance is cloned. Also added the prototype or the clone 
        method.
      storage/myisammrg/myrg_open.c:
        Since we do now again use myrg_open() in the server
        removed the comments marking this as deadcode.
      e80537b7