1. 11 Oct, 2006 5 commits
    • unknown's avatar
      Merge aelkin@bk-internal.mysql.com:/home/bk/mysql-5.0-rpl · 00a34b62
      unknown authored
      into  dsl-hkigw8-feb9fb00-191.dhcp.inet.fi:/home/elkin/MySQL/TEAM/BARE/5.0
      
      
      00a34b62
    • unknown's avatar
      bug#20697 - results in sync with the test · 5d7fb619
      unknown authored
      5d7fb619
    • unknown's avatar
      Merge abarkov@bk-internal.mysql.com:/home/bk/mysql-5.0-rpl · 3daec06d
      unknown authored
      into  mysql.com:/usr/home/bar/mysql-5.0-rpl.b22052
      
      
      3daec06d
    • unknown's avatar
      Merge aelkin@bk-internal.mysql.com:/home/bk/mysql-5.0-rpl · cf1418b4
      unknown authored
      into  dsl-hkigw8-feb9fb00-191.dhcp.inet.fi:/home/elkin/MySQL/TEAM/BARE/5.0
      
      
      cf1418b4
    • unknown's avatar
      BUG#20697 slave fails to rollback replicated transaction hang over innodb_lock_wait_timeou · d6bc2d60
      unknown authored
      Transaction on the slave sql thread got blocked against a slave's mysqld local ta's
      lock. Since the default, slave-transaction-retries=10, there was replaying of the 
      replicated ta. That failed because of a new started from 5.0.13 policy not to rollback
      a timed-out transaction. Effectively the first round of a timed-out ta becomes committed
      by the replaying's first "BEGIN".
      
      It was decided to backport already existed method working in 5.1 implemented in
      bug #16228 for handling symmetrical deadlock problem. That patch introduced end_trans
      execution whenever a replicated ta deadlocks or timed-out.
      
      Note, that this solution can be practically suboptimal - in the light of the changed behavior
      due to timeout we still could replay only the last statement -  only with a high rate of timeouting
      replicated transactions.
      
      
      mysql-test/r/rpl_deadlock.result:
        results changed
      mysql-test/t/rpl_deadlock.test:
        Refining the timeout part of the test to display that the timed-out transaction
        is rolled back prior its replaying by slave sql.
        Non-zero select's count would mean the first round work became persistent - wrong.
      sql/slave.cc:
        applying bug#16228 fix, approbated for deadlock use case in 5.1, almost verbatim. 
        Another alternative to replay only the offending statement requires significant
        efforts, incl design work.
      d6bc2d60
  2. 10 Oct, 2006 1 commit
  3. 08 Oct, 2006 1 commit
  4. 06 Oct, 2006 8 commits
  5. 05 Oct, 2006 3 commits
    • unknown's avatar
      Merge mysql.com:/home/svoj/devel/mysql/BUG21381/mysql-4.1-engines · d4b77025
      unknown authored
      into  mysql.com:/home/svoj/devel/mysql/BUG21381/mysql-5.0-engines
      
      
      mysql-test/r/ndb_update.result:
        Auto merged
      mysql-test/t/ndb_update.test:
        Auto merged
      sql/sql_update.cc:
        Manual merge.
      d4b77025
    • unknown's avatar
      Merge svojtovich@bk-internal.mysql.com:/home/bk/mysql-4.1-engines · 9387a593
      unknown authored
      into  mysql.com:/home/svoj/devel/mysql/BUG21381/mysql-4.1-engines
      
      
      9387a593
    • unknown's avatar
      BUG#21381 - Engine not notified about multi-table UPDATE IGNORE · 2268afed
      unknown authored
      Though this is not storage engine specific problem, I was able to
      repeat this problem with BDB and NDB engines only. That was the
      reason to add a test case into ndb_update.test. As a result
      different bad things could happen.
      
      BDB has removed duplicate rows which is not expected.
      NDB returns an error.
      
      For multi table update notify storage engine about UPDATE IGNORE
      as it is done in single table UPDATE.
      
      
      mysql-test/r/ndb_update.result:
        A test case for bug#21381.
      mysql-test/t/ndb_update.test:
        A test case for bug#21381.
      sql/sql_update.cc:
        For multi table update notify storage engine about UPDATE IGNORE
        as it is done in single table UPDATE.
      2268afed
  6. 03 Oct, 2006 4 commits
    • unknown's avatar
      Merge mysql.com:/usr/home/bar/mysql-4.1-rpl.b8663 · 90316529
      unknown authored
      into  mysql.com:/usr/home/bar/mysql-5.0-rpl
      
      
      myisam/mi_key.c:
        Auto merged
      myisam/mi_open.c:
        Auto merged
      mysql-test/r/ctype_ucs.result:
        Auto merged
      mysql-test/t/ctype_ucs.test:
        After merge fix
      90316529
    • unknown's avatar
      Bug#22052 Trailing spaces are not removed from UNICODE fields in an index · de70be9d
      unknown authored
        Fix: using charset-aware functions cs->cset->lengthsp() and cs->cset->fill()
        instead of single byte code which is not UCS2 compatible.
      
      
      myisam/mi_key.c:
        Using character-set aware functions to trim and append spaces.
      myisam/mi_open.c:
        Initialize charset for BINARY/VARBINARY to my_charset_bin,
            instead of NULL
      mysql-test/r/ctype_ucs.result:
        Adding test case
      mysql-test/t/ctype_ucs.test:
        Adding test case
      de70be9d
    • unknown's avatar
      Merge mysql.com:/usr/home/bar/mysql-4.1-rpl.b8663 · c317c2d2
      unknown authored
      into  mysql.com:/usr/home/bar/mysql-5.0-rpl
      
      
      mysql-test/r/cast.result:
        null merge for bug#8663
        It will beed another fix for 5.0
        - changes in new DECIMAL instead of FLOAT
      mysql-test/r/ps.result:
        null merge
      mysql-test/t/cast.test:
        null merge
      mysql-test/t/count_distinct3.test:
        null merge
      sql/item_func.cc:
        null merge
      c317c2d2
    • unknown's avatar
      Merge mysql.com:/usr/home/bar/mysql-4.1.b8663 · dc62ff55
      unknown authored
      into  mysql.com:/usr/home/bar/mysql-4.1-rpl
      
      
      mysql-test/r/cast.result:
        Auto merged
      mysql-test/r/ps.result:
        Auto merged
      sql/item_func.cc:
        Auto merged
      dc62ff55
  7. 02 Oct, 2006 6 commits
  8. 29 Sep, 2006 12 commits