1. 24 Mar, 2010 3 commits
  2. 23 Mar, 2010 4 commits
  3. 22 Mar, 2010 5 commits
  4. 19 Mar, 2010 2 commits
  5. 18 Mar, 2010 1 commit
  6. 16 Mar, 2010 1 commit
    • Joerg Bruehe's avatar
      Fix a syntax error: · 8b3a95c4
      Joerg Bruehe authored
      A variable declaration was preceded by "DBUG_PRINT()".
      
      sql-common/client.c:
        Thou shalt not declare a variable after an executable statement
        (and "DBUG_PRINT()" is executable).
      8b3a95c4
  7. 15 Mar, 2010 3 commits
  8. 13 Mar, 2010 1 commit
  9. 12 Mar, 2010 6 commits
  10. 11 Mar, 2010 7 commits
  11. 10 Mar, 2010 7 commits
    • Luis Soares's avatar
      Fix for BUG#51716 and BUG#51787: test case improvements. · a7c0e6e4
      Luis Soares authored
      Split rpl_row_charset into:
      
        - rpl_row_utf16.
        - rpl_row_utf32.
      
      This way these tests can run independently if server supports
      either one of the charsets but not both.
      
      Cleaned up rpl_row_utf32 which had a spurious instruction:
      -- let $reset_slave_type_conversions= 0
      a7c0e6e4
    • Davi Arnaut's avatar
      Automatic merge. · 9a08e823
      Davi Arnaut authored
      9a08e823
    • Luis Soares's avatar
      Fix for BUG#51716 and BUG#51787. · 496562f1
      Luis Soares authored
      In BUG#51787 we were using the wrong charset to print out the
      data. We were using the field charset for the string that would
      hold the information. This caused the assertion, because the
      string length was not aligned with UTF32 bytes requirements for
      storage.
      
      We fix this by using &my_charset_latin1 in the string object
      instead of the field->charset(). As a side-effect, we needed to
      extend the show_sql_type interface so that it took the field
      charset is now passed as a parameter, so that one is able to
      calculate the correct field size.
      
      In BUG#51716 we had issues with Field_string::pack and
      Field_string::unpack. When packing, the length was incorrectly
      calculated. When unpacking, the padding the string would be
      padded with the wrong bytes (a few bytes less than it should).
      
      We fix this by resorting to charset abstractions (functions) that
      calculate the correct length when packing and pad correctly the
      string when unpacking.
      496562f1
    • Joerg Bruehe's avatar
      Automerge into next-mr-bugfixing. · 9ce490c8
      Joerg Bruehe authored
      9ce490c8
    • Alexander Nozdrin's avatar
      5bdd80fa
    • Konstantin Osipov's avatar
      A fix and a test case for Bug#51710 FLUSH TABLES <view> WITH READ · a8838f14
      Konstantin Osipov authored
      LOCK kills the server.
      
      Prohibit FLUSH TABLES WITH READ LOCK application to views or
      temporary tables.
      Fix a subtle bug in the implementation when we actually
      did not remove table share objects from the table cache after 
      acquiring exclusive locks.
      
      mysql-test/r/flush.result:
        Update results (Bug#51710)
      mysql-test/t/flush.test:
        Add a test case for Bug#51710.
      sql/sql_parse.cc:
        Fix Bug#51710 "FLUSH TABLES <view> WITH READ LOCK
        killes the server.
        Ensure we don't open views and temporary tables.
        Fix a yet another bug in the implementation which 
        did not actually remove the tables from cache after acquiring
        exclusive locks.
      a8838f14
    • Davi Arnaut's avatar
      Bug#33669: Transactional temporary tables do not work under --read-only · 6f9a684a
      Davi Arnaut authored
      The problem was that in read only mode (read_only enabled),
      the server would mistakenly deny data modification attempts
      for temporary tables which belong to a transactional storage
      engine (eg. InnoDB).
      
      The solution is to allow transactional temporary tables to be
      modified under read only mode. As a whole, the read only mode
      does not apply to any kind of temporary table.
      
      
      mysql-test/r/read_only_innodb.result:
        Add test case result for Bug#33669
      mysql-test/t/read_only_innodb.test:
        Add test case for Bug#33669
      sql/lock.cc:
        Rename mysql_lock_tables_check to lock_tables_check and make
        it static. Move locking related checks from get_lock_data to
        lock_tables_check. Allow write locks to temporary tables even
        under read-only.
      6f9a684a