1. 27 Mar, 2006 1 commit
    • jan's avatar
      Setting a isolation level of the transaction to read committed · 1bd22ab3
      jan authored
      weakens the locks for this session similarly like the option
      innodb_locks_unsafe_for_binlog. This patch removes almost all
      gap locking (used in next-key locking) and makes MySQL to release
      the row locks on the rows which does not belong to result set.
      Additionally, nonlocking selects on INSERT INTO SELECT,
      UPDATE ... (SELECT ...), and CREATE ... SELECT ... use a
      nonlocking consistent read. If a binlog is used, then binlog
      format should be set to row based binloging to make the execution
      of the complex SQL statements.
      1bd22ab3
  2. 22 Mar, 2006 3 commits
  3. 21 Mar, 2006 4 commits
  4. 17 Mar, 2006 3 commits
  5. 16 Mar, 2006 1 commit
  6. 15 Mar, 2006 1 commit
    • marko's avatar
      Merge r328 from branches/5.0: · 2a574b90
      marko authored
      Remove UNIV_RELEASE_NOT_YET_STABLE and related checks.
      
      page_rec_is_comp(): Remove the bounds check.
      
      row_sel_field_store_in_mysql_format(): Turn the assertions on mbminlen,
      mbmaxlen and templ->type into debug assertions.
      2a574b90
  7. 14 Mar, 2006 1 commit
  8. 13 Mar, 2006 2 commits
  9. 10 Mar, 2006 6 commits
  10. 08 Mar, 2006 1 commit
    • osku's avatar
      Port r292 from branches/fts: · 7a50ba7f
      osku authored
      Move printing of dfield_t values from dtuple_print to a new function,
      dfield_print_raw.
      7a50ba7f
  11. 07 Mar, 2006 2 commits
  12. 06 Mar, 2006 2 commits
  13. 02 Mar, 2006 2 commits
  14. 01 Mar, 2006 1 commit
    • jan's avatar
      Fix for bug #12456: Cursor shows incorrect data - DML does not affect, · e671330b
      jan authored
      probably caching. Fixed test results.
      
      This patch implements a high-granularity read view to be used with
      cursors. In this high-granularity consistent read view modifications 
      done by the creating transaction after the cursor is created or 
      future transactions are not visible. But those modifications that 
      transaction did before the cursor was created are visible.
      e671330b
  15. 28 Feb, 2006 1 commit
  16. 27 Feb, 2006 1 commit
  17. 24 Feb, 2006 3 commits
  18. 23 Feb, 2006 2 commits
  19. 22 Feb, 2006 2 commits
  20. 21 Feb, 2006 1 commit