An error occurred fetching the project authors.
  1. 08 Nov, 2013 1 commit
    • Michael Widenius's avatar
      MDEV-5241: Collation incompatibilities with MySQL-5.6 · 192678e7
      Michael Widenius authored
      - Character set code & tests from Alexander Barkov
      - Integration with ALTER TABLE, REPAIR and open_table from Monty
      
      The problem was that MySQL 5.6 added some croatian and vitanamese character set collations that are incompatible with MariaDB.
      
      The fix is to move the MariaDB conflicting collation numbers out of the region that MySQL is likely to use.
      mysql_upgrade, REPAIR TABLE or ALTER TABLE will fix the collations.
      If one tries to access and old incompatible table, one will get the error "Table upgrade required...."
      After this patch, MariaDB supports all the MySQL character set collations and the old MariaDB croatian collations, which are closer to the latest standard than the MySQL versions.
      
      New character sets:
      ucs2_croatian_mysql561_uca_ci
      utf8_croatian_mysql561_uca_ci
      utf16_croatian_mysql561_uca_ci
      utf32_croatian_mysql561_uca_ci
      utf8mb4_croatian_mysql561_uca_ci
      
      Other things:
      - Fixed some compiler warnings
      - mysql_upgrade prints information about repaired tables.
      - Increased version number
      
      VERSION:
        Increased VERSION number
      client/mysqlcheck.c:
        Print repaired table name when using --verbose
      include/m_ctype.h:
        Add new MariaDB collation regions that are not likely to conflict with MySQL
      include/my_base.h:
        Added flag to detect if table was opened for ALTER TABLE
      mysql-test/r/ctype_ldml.result:
        Updated result
      mysql-test/r/ctype_uca.result:
        Updated result
      mysql-test/r/ctype_upgrade.result:
        Updated result
      mysql-test/r/ctype_utf16_uca.result:
        Updated result
      mysql-test/r/ctype_utf32_uca.result:
        Updated result
      mysql-test/r/ctype_utf8mb4_uca.result:
        Updated result
      mysql-test/std_data/ctype_upgrade:
        Test files for testing upgrading of conflicting collations
      mysql-test/suite/engines/funcs/r/db_alter_collate_ascii.result:
        New collations added
      mysql-test/suite/engines/funcs/r/db_alter_collate_utf8.result:
        New collations added
      mysql-test/suite/innodb/r/innodb_ctype_ldml.result:
        Updated test result
      mysql-test/suite/innodb/t/innodb_ctype_ldml.test:
        Updated test result
      mysql-test/suite/plugins/r/show_all_plugins.result:
        Updated version number
      mysql-test/suite/roles/create_and_drop_role_invalid_user_table.result:
        Updated version number
      mysql-test/t/ctype_ldml.test:
        Updated test
      mysql-test/t/ctype_uca.test:
        Testing of new collations
      mysql-test/t/ctype_upgrade.test:
        Testing of upgrading tables with old collations
        The test ensures that:
        - We will get an error if we try to open a table with old collations.
        - CHECK TABLE will detect that the table needs to be upgraded.
        - ALTER TABLE and REPAIR will fix the table.
        - mysql_upgrade works as expected
      mysql-test/t/ctype_utf16_uca.test:
        Testing of new collations
      mysql-test/t/ctype_utf32_uca.test:
        Testing of new collations
      mysql-test/t/ctype_utf8mb4_uca.test:
        Testing of new collations
      mysys/charset-def.c:
        Added new character sets
      mysys/charset.c:
        Always give an error, if requested, if a character set didn't exist
      sql/handler.cc:
        - Added upgrade_collation() to check if collation is compatible with old version
        - check_collation_compatibility() checks if we are using an old collation from MariaDB 5.5 or MySQL 5.6
        - ha_check_for_upgrade() returns HA_ADMIN_NEEDS_ALTER if we have an incompatible collation
      sql/handler.h:
        Added new prototypes
      sql/sql_table.cc:
        - Mark that tables are opened for ALTER TABLE
        - If table needs to be upgraded, ensure we are not using online alter table.
      sql/table.cc:
        - If we are using an old incompatible collation, change to use the new one and mark table as incompatible.
        - Give an error if we try to open an incompatible table.
      sql/table.h:
        Added error that table needs to be rebuild
      storage/connect/ha_connect.cc:
        Fixed compiler warning
      strings/ctype-uca.c:
        New character sets
      192678e7
  2. 05 Nov, 2013 1 commit
  3. 19 Sep, 2013 1 commit
  4. 14 Aug, 2013 1 commit
  5. 06 May, 2013 1 commit
  6. 21 Apr, 2013 1 commit
  7. 09 Mar, 2013 1 commit
  8. 05 Mar, 2013 1 commit
  9. 08 Jan, 2013 1 commit
  10. 27 Nov, 2012 1 commit
  11. 03 Nov, 2012 1 commit
  12. 01 Oct, 2012 1 commit
  13. 24 Aug, 2012 1 commit
  14. 11 Jul, 2012 1 commit
  15. 28 Jun, 2012 1 commit
    • Joerg Bruehe's avatar
      Bug#65745: UPDATE ON INNODB TABLE ENTERS RECURSION · 59c79cc5
      Joerg Bruehe authored
      Introduction of cost based decision on filesort vs index for UPDATE
      statements changed detection of the fact that the index used to scan the
      table is being updated. The new design missed the case of index merge
      when there is no single index to check. That was worked until a recent
      change in InnoDB after which it went into infinite recursion if update of
      the used index wasn't properly detected.
      
      The fix consists of 'used key being updated' detection code from 5.1.
      
      Patch done by Evgeny Potemkin <evgeny.potemkin@oracle.com>
      and transferred into the 5.5.25a release build by Joerg Bruehe.
      
      This changeset is the difference between MySQL 5.5.25 and 5.5.25a.
      
      
      VERSION:
        Version number change.
      sql/sql_update.cc:
        Bug#65745: UPDATE ON INNODB TABLE ENTERS RECURSION
        The check for used key being updated is extended to cover the case when
        index merge is used.
      59c79cc5
  16. 15 Jun, 2012 1 commit
  17. 31 May, 2012 1 commit
    • Michael Widenius's avatar
      Increased the version number to 10.0 · 83c02f32
      Michael Widenius authored
      - Fixed code that was not ready for a major version number > 9
      - Fixed test cases that assumed max major version number could be 9
      Updated version number for depricated options (will be removed in a later commit)
      
      VERSION:
        Version number 10.0.0
      client/mysqlbinlog.cc:
        Added support for major version numbers > 9
      cmake/mysql_version.cmake:
        Added support for version numbers that is 0
      mysql-test/r/comments.result:
        Modified test to handle version number 100000
      mysql-test/r/func_system.result:
        Modified test to handle version number 100000
      mysql-test/r/log_state.result:
        Updated depricated error message
      mysql-test/r/sp.result:
        Modified test to handle version number 100000
      mysql-test/r/subselect4.result:
        Updated depricated error message
      mysql-test/r/variables.result:
        Updated depricated error message
      mysql-test/suite/rpl/r/rpl_conditional_comments.result:
        Modified test to handle version number 100000
      mysql-test/suite/rpl/r/rpl_loaddatalocal.result:
        Modified test to handle version number 100000
      mysql-test/suite/rpl/t/rpl_conditional_comments.test:
        Modified test to handle version number 100000
      mysql-test/suite/rpl/t/rpl_loaddatalocal.test:
        Modified test to handle version number 100000
      mysql-test/suite/sys_vars/r/debug_basic.result:
        Updated depricated error message
      mysql-test/suite/sys_vars/r/engine_condition_pushdown_basic.result:
        Updated depricated error message
      mysql-test/suite/sys_vars/r/log_basic.result:
        Updated depricated error message
      mysql-test/suite/sys_vars/r/log_slow_queries_basic.result:
        Updated depricated error message
      mysql-test/suite/sys_vars/r/multi_range_count_basic.result:
        Updated depricated error message
      mysql-test/suite/sys_vars/r/rpl_recovery_rank_basic.result:
        Updated depricated error message
      mysql-test/suite/sys_vars/r/sql_big_selects_func.result:
        Updated depricated error message
      mysql-test/suite/sys_vars/r/sql_max_join_size_basic.result:
        Updated depricated error message
      mysql-test/suite/sys_vars/r/sql_max_join_size_func.result:
        Updated depricated error message
      mysql-test/t/comments.test:
        Modified test to handle version number 100000
      mysql-test/t/file_contents.test:
        Modified test to handle version number 100000
      mysql-test/t/func_system.test:
        Modified test to handle version number 100000
      mysql-test/t/parser_not_embedded.test:
        Modified test to handle version number 100000
      mysql-test/t/sp.test:
        Modified test to handle version number 100000
      sql/mysqld.cc:
        Updated version number for depricated options (will be removed in a later commit)
      sql/slave.cc:
        Modified test to handle version number 100000
        Better error messages
      sql/sql_lex.cc:
        Modified test to handle version number 100000 in comment syntax
      sql/sys_vars.cc:
        Updated version number for depricated options (will be removed in a later commit)
      83c02f32
  18. 14 May, 2012 1 commit
  19. 16 Apr, 2012 1 commit
  20. 29 Mar, 2012 1 commit
  21. 20 Feb, 2012 2 commits
  22. 30 Jan, 2012 1 commit
  23. 16 Dec, 2011 1 commit
  24. 23 Nov, 2011 2 commits
  25. 26 Oct, 2011 2 commits
  26. 27 Sep, 2011 1 commit
  27. 12 Aug, 2011 1 commit
  28. 13 Jul, 2011 1 commit
  29. 02 Jul, 2011 1 commit
  30. 10 Jun, 2011 1 commit
  31. 09 Jun, 2011 1 commit
  32. 13 May, 2011 1 commit
  33. 11 May, 2011 1 commit
  34. 11 Apr, 2011 1 commit
  35. 21 Mar, 2011 1 commit
  36. 11 Feb, 2011 1 commit
  37. 14 Jan, 2011 1 commit