1. 27 Sep, 2007 1 commit
  2. 29 Aug, 2007 2 commits
  3. 28 Aug, 2007 1 commit
    • gkodinov/kgeorge@magare.gmz's avatar
      Bug #30377: EXPLAIN loses last_query_cost when used with UNION · cfaa0983
      gkodinov/kgeorge@magare.gmz authored
      Currently the Last_query_cost session status variable shows
      only the cost of a single flat subselect. For complex queries
      (with subselects or unions etc) Last_query_cost is not valid
      as it was showing the cost for the last optimized subselect.
      Fixed by reseting to zero Last_query_cost when the complete
      cost of the query cannot be determined.
      Last_query_cost will be non-zero only for single flat queries.
      cfaa0983
  4. 27 Aug, 2007 1 commit
    • mhansson/martin@linux-st28.site's avatar
      Bug #30596 GROUP BY optimization gives wrong result order · a4d5d920
      mhansson/martin@linux-st28.site authored
      The optimization that uses a unique index to remove GROUP BY, did not 
      ensure that the index was actually used, thus violating the ORDER BY
      that is impled by GROUP BY.
      Fixed by replacing GROUP BY with ORDER BY if the GROUP BY clause contains
      a unique index. In case GROUP BY ... ORDER BY null is used, GROUP BY is
      simply removed.
      a4d5d920
  5. 26 Aug, 2007 1 commit
  6. 25 Aug, 2007 3 commits
  7. 24 Aug, 2007 8 commits
  8. 23 Aug, 2007 2 commits
  9. 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
  10. 21 Aug, 2007 10 commits
  11. 20 Aug, 2007 4 commits
  12. 18 Aug, 2007 1 commit
  13. 17 Aug, 2007 2 commits