1. 21 Aug, 2007 1 commit
    • thek@adventure.(none)'s avatar
      Bug#30269 Query cache eats memory · acfe3fc9
      thek@adventure.(none) authored
      Although the query cache doesn't support retrieval of statements containing
      column level access control, it was still possible to cache such statements
      thus wasting memory.
        
      This patch extends the access control check on the target tables to avoid
      caching a statement with column level restrictions. 
      
      Views are excepted and can be cached but only retrieved by super user account.
      acfe3fc9
  2. 17 Aug, 2007 1 commit
    • thek@adventure.(none)'s avatar
      Bug #30269 Query cache eats memory · a4248c2d
      thek@adventure.(none) authored
      Although the query cache doesn't support retrieval of statements containing
      column level access control, it was still possible to cache such statements
      thus wasting memory.
      
      This patch extends the access control check on the target tables to avoid
      caching a statement with column level restrictions. 
      a4248c2d
  3. 27 Jul, 2007 1 commit
    • thek@adventure.(none)'s avatar
      Bug #29929 LOCK TABLES does not pre-lock tables used in triggers of the locked tables · 889b4ebc
      thek@adventure.(none) authored
      When a table was explicitly locked with LOCK TABLES no associated
      tables from any related trigger on the subject table were locked.
      As a result of this the user could experience unexpected locking
      behavior and statement failures similar to "failed: 1100: Table'xx'
      was not locked with LOCK TABLES".
      
      This patch fixes this problem by making sure triggers are
      pre-loaded on any statement if the subject table was explicitly
      locked with LOCK TABLES.
      889b4ebc
  4. 24 Jul, 2007 1 commit
  5. 21 Jul, 2007 1 commit
  6. 20 Jul, 2007 5 commits
  7. 19 Jul, 2007 16 commits
  8. 18 Jul, 2007 7 commits
  9. 17 Jul, 2007 7 commits