1. 09 Nov, 2007 1 commit
    • cmiller@zippy.cornsilk.net's avatar
      Rewrite profiler code to be easier to maintain and less buggy. · f12087af
      cmiller@zippy.cornsilk.net authored
      Between 5.0 and 5.1, the step of incrementing the global query id
      changed, which broke how the profiler noticed when a new query had
      started.  That reset the state list and caused all but the last 
      five (or so) states to be thrown away.
      
      Now, don't watch for query_id changes in the lower level.
      
      Add a bogus state change at the end of profiling so that the last 
      real state change is timed.
      
      Emit source reference for the start of the span of time instead of
      the end of it.
      f12087af
  2. 02 Nov, 2007 2 commits
  3. 31 Oct, 2007 4 commits
  4. 30 Oct, 2007 8 commits
  5. 29 Oct, 2007 14 commits
  6. 26 Oct, 2007 1 commit
    • mleich@four.local.lan's avatar
      Fix for · d3e18cc9
      mleich@four.local.lan authored
         Bug#31408 funcs_1: <engine>_trig_03e test fail
      Modification:
         The TRIGGER PRIVILEGE is now needed for getting informations about TRIGGERs.
         Therefore after REVOKE TRIGGER privilege the 
         - SHOW TRIGGERS
         - SELECT * FROM INFORMATION_SCHEMA.TRIGGERS
         result sets are now empty.
      d3e18cc9
  7. 25 Oct, 2007 4 commits
  8. 24 Oct, 2007 1 commit
  9. 23 Oct, 2007 5 commits