1. 04 Jul, 2008 1 commit
    • Sven Sandberg's avatar
      BUG#37858: loaddata,rpl_slave_skip,rpl_innodb_mixed_dml fail if datafile not world-readable · eb05cd9e
      Sven Sandberg authored
      Problem 1: main.loaddata tried to trigger an error caused by
      reading files outside the vardir, by reading itself. However,
      if loaddata.test is not world-readable (e.g., umask=0077),
      then another error is triggered.
      Fix 1: allow the other error too.
      Problem 2: rpl_slave_skip and rpl_innodb_mixed_dml tried to
      copy a file from mysql-test/suite/rpl/data to mysql-test/var
      and then read it. That failed too if umask=0077, since the
      file would not become world-readable.
      Fix 2: move the files from mysql-test/suite/rpl/data to
      mysql-test/std_data and update tests accordingly. Remove
      the directory mysql-test/suite/rpl/data.
      eb05cd9e
  2. 19 Jun, 2008 3 commits
  3. 18 Jun, 2008 5 commits
    • Magnus Svensson's avatar
      Fix paths · 755e0157
      Magnus Svensson authored
      755e0157
    • Magnus Svensson's avatar
      Merge · cafa042a
      Magnus Svensson authored
      cafa042a
    • Timothy Smith's avatar
    • Timothy Smith's avatar
      fix typo · 3847e5c8
      Timothy Smith authored
      This change was committed to the 5.1.25 release clone, but never
      made it to the mysql-5.1 BK tree.  I'm committing it to mysql-5.1
      bzr now.
      3847e5c8
    • Timothy Smith's avatar
      Bug #37024: Wrong location of messagefiles · aa45d0c0
      Timothy Smith authored
      make_binary_distribution.sh got clobbered by the 5.0 version during a merge.
      This caused a few packaging problems, including message files put in the wrong
      place and some missing files.  Fix is just to revert back to the 5.1 version
      from before the merge.
      
      Problem introduced in
      ChangeSet 1.2606.2.1 2008/05/13 15:56:07 kent@kent-amd64.(none)
      
      This change was made in the 5.1.25 release clone in BK, but never made it to the main mysql-5.1 BK tree.  I am adding it to mysql-5.1 bzr.
      aa45d0c0
  4. 16 Jun, 2008 2 commits
    • Magnus Svensson's avatar
      WL#4189 · 88e3cebc
      Magnus Svensson authored
       - Increase start timeout to 180 seconds, old version had 400 that is too much
      88e3cebc
    • Magnus Svensson's avatar
      WL#4189 · b15f4190
      Magnus Svensson authored
       - Fix make_binary_distribution.sh after removing mysql-test/ndb dir
      b15f4190
  5. 03 Jun, 2008 2 commits
  6. 30 May, 2008 2 commits
  7. 22 May, 2008 2 commits
  8. 21 May, 2008 2 commits
  9. 20 May, 2008 8 commits
  10. 19 May, 2008 3 commits
  11. 18 May, 2008 5 commits
    • gshchepa/uchum@host.loc's avatar
      Merge host.loc:/work/bk/5.0-bugteam · d044d9f0
      gshchepa/uchum@host.loc authored
      into  host.loc:/work/bk/5.1-bugteam
      d044d9f0
    • gshchepa/uchum@host.loc's avatar
      Merge host.loc:/work/bugs/5.0-bugteam-36676 · 80b16212
      gshchepa/uchum@host.loc authored
      into  host.loc:/work/bk/5.0-bugteam
      80b16212
    • gshchepa/uchum@host.loc's avatar
      Fixed bug#36676: multiupdate using LEFT JOIN updates only · 2459d3a9
      gshchepa/uchum@host.loc authored
                       first row or fails with an error:
        ERROR 1022 (23000): Can't write; duplicate key in table ''
      
      The server uses intermediate temporary table to store updated
      row data.  The first column of this table contains rowid.
      Current server implementation doesn't reset NULL flag of that
      column even if the server fills a column with rowid.
      To keep each rowid unique, there is an unique index.
      An insertion into an unique index takes into account NULL
      flag of key value and ignores real data if NULL flag is set.
      So, insertion of actually different rowids may lead to two
      kind of problems.  Visible effect of each of these problems
      depends on an initial engine type of temporary table:
      
      1. If multiupdate initially creates temporary table as
      a MyISAM table (a table contains blob columns, and the
      create_tmp_table function assumes, that this table is
      large), it inserts only one single row and updates
      only rows with one corresponding rowid. Other rows are
      silently ignored. 
      
      2. If multiupdate initially creates MEMORY temporary
      table, fills it with data and reaches size limit for
      MEMORY tables (max_heap_table_size), multiupdate
      converts MEMORY table into MyISAM table and fails
      with an error:
        ERROR 1022 (23000): Can't write; duplicate key in table ''
      
      
      Multiupdate has been fixed to update the NULL flag of
      temporary table rowid columns.
      2459d3a9
    • gkodinov/kgeorge@magare.gmz's avatar
      Merge magare.gmz:/home/kgeorge/mysql/work/mysql-5.0-bugteam · faa13308
      gkodinov/kgeorge@magare.gmz authored
      into  magare.gmz:/home/kgeorge/mysql/work/merge-5.1-bugteam
      faa13308
    • kostja@bodhi.(none)'s avatar
      Fix mysql_client_test failure in pushbuild 5.1-27430 · aef39682
      kostja@bodhi.(none) authored
      (Bug#27430)
      aef39682
  12. 17 May, 2008 2 commits
  13. 16 May, 2008 3 commits