1. 13 Apr, 2009 1 commit
  2. 10 Apr, 2009 4 commits
    • Chad MILLER's avatar
      Merge fix for bug 39559 and bugteam trunk. · 538fdd3d
      Chad MILLER authored
      538fdd3d
    • Sergey Glukhov's avatar
      Bug#43385 Cannot ALTER DATABASE ... UPGRADE DATA DIRECTORY NAME when Views exist · 5c5691e8
      Sergey Glukhov authored
      allow 'rename view' for ALTER ...UPGRADE DATA DIRECTORY NAME command.
      it's safe because a view has valid internal db&table names in this case.
      5c5691e8
    • Narayanan V's avatar
      Bug#44020 Unicode Swedish collations not working with IBMDB2I · 39d9d106
      Narayanan V authored
      The utf8_swedish_ci and ucs2_swedish_ci
      collations do not work with indexes on 
      IBMDB2I tables.
      
      The current patch adds the mapping for
      ucs2_swedish collation and removes the 
      ucs2_spanish2 mapping which is not
      supported by any version of the operating
      system.
      39d9d106
    • Chad MILLER's avatar
      Bug#39559: dump of stored procedures / functions with C-style \ · aa449c10
      Chad MILLER authored
      	comment can't be read back
      
      A change to the lexer in 5.1 caused slash-asterisk-bang-version
      sections to be terminated early if there exists a slash-asterisk-
      style comment inside it.  Nesting comments is usually illegal,
      but we rely on versioned comment blocks in mysqldump, and the
      contents of those sections must be allowed to have comments.
      
      The problem was that when encountering open-comment tokens and
      consuming -or- passing through the contents, the "in_comment"
      state at the end was clobbered with the not-in-a-comment value,
      regardless of whether we were in a comment before this or not.  
      
      So, """/*!VER one /* two */ three */""" would lose its in-comment
      state between "two" and "three".  Save the echo and in-comment
      state, and restore it at the end of the comment if we consume a 
      comment.
      aa449c10
  3. 09 Apr, 2009 19 commits
  4. 08 Apr, 2009 8 commits
  5. 07 Apr, 2009 5 commits
  6. 06 Apr, 2009 2 commits
  7. 05 Apr, 2009 1 commit
    • Alfranio Correia's avatar
      BUG#39393 slave-skip-errors does not work when using ROW based replication · 1287d8c5
      Alfranio Correia authored
                                    
      RBR was not considering the option --slave-skip-errors.
                                    
      To fix the problem, we are reporting the ignored ERROR(s) as warnings thus avoiding 
      stopping the SQL Thread. Besides, it fixes the output of "SHOW VARIABLES LIKE 
      'slave_skip_errors'" which was showing nothing when the value "all" was assigned 
      to --slave-skip-errors.
                        
      @sql/log_event.cc
        skipped rbr errors when the option skip-slave-errors is set.
      @sql/slave.cc
        fixed the output of for SHOW VARIABLES LIKE 'slave_skip_errors'"
      @test-cases
        fixed the output of rpl.rpl_idempotency
        updated the test case rpl_skip_error
      1287d8c5