An error occurred fetching the project authors.
  1. 04 Jan, 2011 1 commit
  2. 03 Nov, 2010 1 commit
    • Marc Alff's avatar
      Bug#57609 performance_schema does not work with lower_case_table_names · 7f35b15a
      Marc Alff authored
      Before this fix, the performance schema tables were defined in UPPERCASE.
      
      This was incompatible with the lowercase_table_names option, and caused
      issues with the install / upgrade process, when changing the lower case
      table names setting *after* the install or upgrade.
      
      With this fix, all performance schema tables are exposed with lowercase names.
      As a result, the name of the performance schema table is always lowercase,
      no matter how / if / when the lowercase_table_names setting if changed.
      7f35b15a
  3. 20 Aug, 2010 1 commit
    • Alfranio Correia's avatar
      BUG#53452 Inconsistent behavior of binlog_direct_non_transactional_updates with · c6d4915f
      Alfranio Correia authored
      temp table
                  
      This patch introduces two key changes in the replication's behavior.
                  
      Firstly, it reverts part of BUG#51894 which puts any update to temporary tables
      into the trx-cache. Now, updates to temporary tables are handled according to
      the type of their engines as a regular table.
                  
      Secondly, an unsafe mixed statement, (i.e. a statement that access transactional
      table as well non-transactional or temporary table, and writes to any of them),
      are written into the trx-cache in order to minimize errors in the execution when
      the statement logging format is in use.
                  
      Such changes has a direct impact on which statements are classified as unsafe
      statements and thus part of BUG#53259 is reverted.
      c6d4915f
  4. 28 Apr, 2010 1 commit
  5. 15 Jan, 2010 1 commit
    • 's avatar
      Fix for perfschema.binlog_stmt failure: · fe99d915
      authored
              
      Problem: The test case failed because: (i) warning text in 
               result file differed from the warning output by the 
               server, and (ii) binlog contents in result file did
               not show the statements logged wrapped in BEGIN/COMMIT
               as it is the case after WL 2687.
            
      Solution: We update the result file, but first we change the
                unsafe warning text to also refer to performance_schema
                table(s). This required changing the result files for
                existing test cases that provide output for warnings 
                related to ER_BINLOG_UNSAFE_SYSTEM_TABLE. "Grepping" in
                result files, shows that only binlog_unsafe contained
                reference to such a warning.
            
                We also update the result file with the missing 
                BEGIN/COMMIT statements.
      fe99d915
  6. 12 Jan, 2010 1 commit