An error occurred fetching the project authors.
  1. 02 Feb, 2009 1 commit
    • Matthias Leich's avatar
      1. Slice of fix for Bug#42003 tests missing the disconnect of connections <> default · 7da691c9
      Matthias Leich authored
         - If missing: add "disconnect <session>"
         - If physical disconnect of non "default" sessions is not finished
           at test end: add routine which waits till this happened
      + additional improvements like
        - remove superfluous files created by the test
        - replace error numbers by error names
        - remove trailing spaces, replace tabs by spaces
        - unify writing of bugs within comments
        - correct comments
        - minor changes of formatting
      Modifications according to the code review are included.
      Fixed tests:
      grant2
      grant3
      lock_tables_lost_commit
      mysqldump
      openssl_1
      outfile
      7da691c9
  2. 27 Sep, 2007 1 commit
  3. 08 Jun, 2007 1 commit
  4. 23 May, 2007 1 commit
    • dlenev@mockturtle.local's avatar
      5.0 version of fix for: · c07b3670
      dlenev@mockturtle.local authored
       Bug #23667 "CREATE TABLE LIKE is not isolated from alteration
                   by other connections"
       Bug #18950 "CREATE TABLE LIKE does not obtain LOCK_open"
      As well as:
       Bug #25578 "CREATE TABLE LIKE does not require any privileges
                   on source table".
      
      The first and the second bugs resulted in various errors and wrong
      binary log order when one tried to execute concurrently CREATE TABLE LIKE
      statement and DDL statements on source table or DML/DDL statements on its
      target table.
      
      The problem was caused by incomplete protection/table-locking against
      concurrent statements implemented in mysql_create_like_table() routine.
      We solve it by simply implementing such protection in proper way (see
      comment for sql_table.cc for details).
      
      The third bug allowed user who didn't have any privileges on table create
      its copy and therefore circumvent privilege check for SHOW CREATE TABLE.
      
      This patch solves this problem by adding privilege check, which was missing.
      
      Finally it also removes some duplicated code from mysql_create_like_table().
      
      Note that, altough tests covering concurrency-related aspects of CREATE TABLE
      LIKE behaviour will only be introduced in 5.1, they were run manually for
      this patch as well.
      c07b3670
  5. 26 Feb, 2007 1 commit
  6. 28 Jun, 2006 1 commit
  7. 18 Apr, 2006 2 commits
  8. 02 Mar, 2006 1 commit
  9. 27 Feb, 2006 1 commit
  10. 26 Jan, 2006 1 commit
  11. 28 Dec, 2005 2 commits
  12. 01 Sep, 2005 1 commit
    • dlenev@mysql.com's avatar
      Fix for bug #12423 "Deadlock when doing FLUSH PRIVILEGES and GRANT in · da2af0bb
      dlenev@mysql.com authored
      multi-threaded environment".
      
      To avoid deadlocks between several simultaneously run account management 
      commands (particularly between FLUSH PRIVILEGES/SET PASSWORD and GRANT
      commands) we should always take table and internal locks during their
      execution in the same order. In other words we should first open and lock
      privilege tables and only then obtain acl_cache::lock/LOCK_grant locks.
      da2af0bb
  13. 22 Aug, 2005 1 commit
  14. 28 Jul, 2005 1 commit
  15. 29 Mar, 2005 2 commits
  16. 27 Mar, 2005 1 commit
  17. 23 Mar, 2005 1 commit
    • serg@serg.mylan's avatar
      sql/sql_acl.cc · 9a0dd5c7
      serg@serg.mylan authored
          report correct errror in MODE_NO_AUTO_CREATE_USER
          cleanup
      after merge fixes
      9a0dd5c7
  18. 22 Mar, 2005 2 commits
  19. 18 Mar, 2005 1 commit
    • jani@a193-229-222-105.elisa-laajakaista.fi's avatar
      Added more tests to grant2. Fixed some previous tests. · 5537d214
      Added new logic to ACL system:
      
      1) If GRANT OPTION (not mysql db):
         Ok to update existing user, but not password.
         Not allowed to make a new user.
      
      2) If UPDATE_ACL to mysql DB:
         Ok to update current user, but not make a new one.
      
      3) If INSERT_ACL to mysql DB:
         Ok to add a new user, but not modify existing.
      
      4) If GRANT OPTION to mysql DB:
         All modifications OK.
      5537d214
  20. 17 Mar, 2005 1 commit
    • jani@a193-229-222-105.elisa-laajakaista.fi's avatar
      Fixed two bugs in MySQL ACL. · 1fbb6175
      First one is related to Bug#7905. One should not be allowed to
      create new user with password without UPDATE privilege to
      MySQL database. Furthermore, executing the same GRANT statement
      twice would actually crash the server and corrupt privilege database.
      
      Other bug was that one could update a column, using the existing
      value as basis to calculate the new value (e.g. UPDATE t1 SET a=a+1)
      without SELECT privilege to the field (a in the above example)
      
      Fixed tests grant.pl and grant2, which were wrong.
      1fbb6175
  21. 04 Mar, 2005 1 commit
  22. 03 Mar, 2005 1 commit
  23. 31 Dec, 2004 2 commits
  24. 23 Dec, 2004 1 commit
  25. 27 Nov, 2004 1 commit
  26. 26 Nov, 2004 1 commit
  27. 25 Nov, 2004 1 commit
  28. 02 Nov, 2004 1 commit
  29. 20 Oct, 2004 1 commit
  30. 08 Jul, 2004 1 commit
  31. 05 Apr, 2004 1 commit
    • gluh@gluh.mysql.r18.ru's avatar
      WL1368: SHOW GRANTS FOR CURRENT USER · 8a4e6c64
      gluh@gluh.mysql.r18.ru authored
        'SHOW GRANTS' syntax is added 
        'SHOW GRANTS FOR CURRENT_USER' syntax is added
        'SHOW GRANTS FOR CURRENT_USER()' syntax is added
       CURRENT_USER without parens in expressions(SELECT CURRENT_USER;) 
      8a4e6c64
  32. 28 Jul, 2003 1 commit
  33. 22 Jul, 2003 2 commits