1. 18 Apr, 2008 3 commits
  2. 17 Apr, 2008 2 commits
  3. 16 Apr, 2008 5 commits
  4. 15 Apr, 2008 2 commits
  5. 14 Apr, 2008 2 commits
  6. 11 Apr, 2008 3 commits
  7. 10 Apr, 2008 9 commits
  8. 09 Apr, 2008 7 commits
  9. 08 Apr, 2008 4 commits
    • aelkin/andrei@mysql1000.(none)'s avatar
      Merge mysqldev@production.mysql.com:my/mysql-5.1-release · 7a8b1bae
      aelkin/andrei@mysql1000.(none) authored
      into  mysql1000.(none):/home/andrei/MySQL/BARE/mysql-5.1-release
      7a8b1bae
    • kent/mysqldev@mysql.com/production.mysql.com's avatar
      Makefile.am: · 9b6ac078
        Add ChangeLog if it exists
        - Removed separate 'normal+rowrepl' test run, not needed any longer
        - Removed separate 'rpl' test run, included in main test run already
        - Renamed some test "comments", to use similar naming style
        - Limited one of the Cluster test runs to 'ndb' and 'rpl_ndb' suites
        - Reordered test runs, to be aligned with Windows test runs
      mysql.spec.sh:
        - No longer including the "Example" storage engine
        - Added to configure "--without-ENGINE" if not to compile engine as plugin
      9b6ac078
    • aelkin/andrei@mysql1000.(none)'s avatar
      Bug #35762 Failing CREATE-SELECT steels Table map of the following query · 725d07d5
      aelkin/andrei@mysql1000.(none) authored
      Among two claimed artifacts the critical one is in that the Table map of 
      a query following the failing with a duplicate key error CREATE-SELECT is skipped from
      instantionating (and thus binlogging). That leads to sending a "chopped" group of the data
      row-events without the table map head to the slave. 
      The slave can not apply the only data row events.
      It's not easy to force the slave to react with an error in such a case (the second complaint
      on the bug report), because the lack of a table Rows_log_event::do_apply_event the data row event
      handler is a common situation which  normally designates the event has to be filtered out
      basing on the repliation do/ingore rules decision.
      
      Fixed: table map creating and binlogging is restored via deploying the standard cleanup call in
      select_create::abort().
      No error is reported if by chance the table map was not been binlogged.
      Leaving this out to resolve with considering how to combine the do/ingore rules with the situation
      when erronoulsy the Table_map is not written to binlog.
      725d07d5
    • ramil/ram@mysql.com/ramil.myoffice.izhnet.ru's avatar
      Fix for bug #35732: read-only blocks SELECT statements in InnoDB · 5397f8c9
      Problem: SELECTs prohibited for a transactional SE in autocommit mode
      if read_only is set.
      
      Fix: allow them.
      5397f8c9
  10. 05 Apr, 2008 2 commits
  11. 04 Apr, 2008 1 commit