1. 03 Oct, 2007 1 commit
  2. 27 Aug, 2007 1 commit
  3. 25 Aug, 2007 1 commit
  4. 24 Aug, 2007 9 commits
  5. 23 Aug, 2007 4 commits
  6. 22 Aug, 2007 4 commits
    • joerg@trift2.'s avatar
      Cleanup in the "netware" subdirectory: · 18b8e7a3
      joerg@trift2. authored
      1) We do not provide the "isam" table handler in 5.0 and up (different from "myisam" !),
         so we do not need the ".def" files for the "isam"-specific tools.
      
      2) Use "basename" to get the base name of a file, not a harder-to-read sed expression.
      18b8e7a3
    • gshchepa/uchum@gleb.loc's avatar
      Merge gleb.loc:/home/uchum/work/bk/5.0-opt-30201 · 16e0a4de
      gshchepa/uchum@gleb.loc authored
      into  gleb.loc:/home/uchum/work/bk/5.0-opt
      16e0a4de
    • jani@hynda.mysql.fi's avatar
      Merge hynda.mysql.fi:/home/my/mysql-5.0-main · 28b2b890
      jani@hynda.mysql.fi authored
      into  hynda.mysql.fi:/home/my/mysql-5.0-marvel
      28b2b890
    • gshchepa/uchum@gleb.loc's avatar
      Fixed bug #30201. · f3d0f62d
      gshchepa/uchum@gleb.loc authored
      Killing a SELECT query with KILL QUERY or KILL CONNECTION
      causes a server crash if the query cache is enabled.
      
      Normal evaluation of a query may be interrupted by the
      KILL QUERY/CONNECTION statement, in this case the mysql_execute_command
      function returns TRUE, and the thd->killed flag has true value.
      In this case the result of the query may
      be cached incompletely (omitting call to query_cache_insert inside
      the net_real_write function), and next call to query_cache_end_of_result
      may lead to server crash.
      Thus, the query_cache_end_of_result function has been modified to abort
      query cache in the case of killed thread.
      f3d0f62d
  7. 21 Aug, 2007 10 commits
  8. 20 Aug, 2007 4 commits
  9. 18 Aug, 2007 1 commit
  10. 17 Aug, 2007 3 commits
  11. 16 Aug, 2007 2 commits