1. 16 May, 2007 1 commit
    • svoj@mysql.com/april.(none)'s avatar
      BUG#25712 - insert delayed and check table run together report crashed · 3ea2ee35
      svoj@mysql.com/april.(none) authored
                  tables
      
      In case system doesn't have native pread/pwrite calls (e.g. Windows)
      and there is CHECK TABLE runs concurrently with another statement that
      reads from a table, the table may be reported as crashed.
      
      This is fixed by locking file descriptor when my_seek is executed on
      MyISAM index file and emulated pread/pwrite may be executed concurrently.
      
      Affects MyISAM tables on platforms that do not have native
      pread/pwrite calls (e.g. Windows).
      
      No deterministic test case for this bug.
      3ea2ee35
  2. 28 Apr, 2007 1 commit
  3. 26 Apr, 2007 2 commits
  4. 24 Apr, 2007 2 commits
  5. 23 Apr, 2007 2 commits
  6. 20 Apr, 2007 1 commit
  7. 19 Apr, 2007 1 commit
  8. 18 Apr, 2007 1 commit
  9. 17 Apr, 2007 3 commits
  10. 14 Apr, 2007 1 commit
  11. 12 Apr, 2007 2 commits
  12. 11 Apr, 2007 4 commits
  13. 10 Apr, 2007 9 commits
  14. 07 Apr, 2007 2 commits
  15. 05 Apr, 2007 3 commits
  16. 04 Apr, 2007 4 commits
  17. 03 Apr, 2007 1 commit
    • igor@olga.mysql.com's avatar
      Fixed bug #27532: wrong results with ORDER/GROUP BY queries containing · 90aa05d2
      igor@olga.mysql.com authored
      IN/BETWEEN predicates in sorting expressions.
      Wrong results may occur when the select list contains an expression
      with IN/BETWEEN predicate that differs from a sorting expression by
      an additional NOT only.
       
      Added the method Item_func_opt_neg::eq to compare correctly expressions
      containing [NOT] IN/BETWEEN.
      The eq method inherited from the Item_func returns TRUE when comparing
      'a IN (1,2)' with 'a NOT IN (1,2)' that is not, of course, correct.  
      90aa05d2