An error occurred fetching the project authors.
  1. 26 Feb, 2007 1 commit
  2. 02 Jan, 2007 1 commit
  3. 11 Dec, 2006 1 commit
    • patg@radha.myhome.westell.com's avatar
      WL #3031 · b892f9ad
      patg@radha.myhome.westell.com authored
      * New result files due to new error message/error numbers
      * Fixed system_mysql_db tests to work with servers table
      * Added UTF8 charset to table defs
      b892f9ad
  4. 01 Dec, 2006 1 commit
  5. 29 Nov, 2006 1 commit
    • msvensson@neptunus.(none)'s avatar
      Bug#20589 Missing some table level privileges after upgrade · dcf0f346
      msvensson@neptunus.(none) authored
       - The table_priv column of table_privs table was altered to a enum type
         with fewer enums causing the SHOW/CREATE VIEW grants to be truncated.
       - Improved comments and moved all declarations for table_privs, column_privs
         and proc_privs to one section for each table making it easy to see hat alterations
         are performed on each table
       - Reduced the number of ALTER's slightly, but as this is an upgrade script we need
         to take all possibilites into account.
      dcf0f346
  6. 22 Nov, 2006 1 commit
  7. 21 Nov, 2006 4 commits
  8. 20 Nov, 2006 1 commit
  9. 29 May, 2006 1 commit
  10. 24 Mar, 2006 1 commit
  11. 24 Feb, 2006 1 commit
  12. 23 Feb, 2006 1 commit
  13. 02 Feb, 2006 1 commit
  14. 01 Feb, 2006 1 commit
    • anozdrin@mysql.com's avatar
      Fix for BUG#9412: Triggers: should have trigger privilege. · 0a1f7e92
      anozdrin@mysql.com authored
      Implement table-level TRIGGER privilege to control access to triggers.
      Before this path global SUPER privilege was used for this purpose, that
      was the big security problem.
      
      In details, before this patch SUPER privilege was required:
        - for the user at CREATE TRIGGER time to create a new trigger;
        - for the user at DROP TRIGGER time to drop the existing trigger;
        - for the definer at trigger activation time to execute the trigger (if the
          definer loses SUPER privilege, all its triggers become unavailable);
      
      This patch changes the behaviour in the following way:
        - TRIGGER privilege on the subject table for trigger is required:
          - for the user at CREATE TRIGGER time to create a new trigger;
          - for the user at DROP TRIGGER time to drop the existing trigger;
          - for the definer at trigger activation time to execute the trigger
            (if the definer loses TRIGGER privilege on the subject table, all its
            triggers on this table become unavailable).
        - SUPER privilege is still required:
          - for the user at CREATE TRIGGER time to explicitly set the trigger
            definer to the user other than CURRENT_USER().
      
      When the server works with database of the previous version (w/o TRIGGER
      privilege), or if the database is being upgraded from the previous versions,
      TRIGGER privilege is granted to whose users, who have CREATE privilege.
      0a1f7e92
  15. 31 Jan, 2006 3 commits
  16. 30 Jan, 2006 1 commit
    • andrey@lmy004.'s avatar
      fix for bug#16642 (Events: No INFORMATION_SCHEMA.EVENTS table) · d847ac54
      andrey@lmy004. authored
      post-review change - use pointer instead of copy on the stack.
      WL#1034 (Internal CRON)
       This patch adds INFORMATION_SCHEMA.EVENTS table with the following format:
        EVENT_CATALOG  - MYSQL_TYPE_STRING  (Always NULL)
        EVENT_SCHEMA   - MYSQL_TYPE_STRING  (the database)
        EVENT_NAME     - MYSQL_TYPE_STRING  (the name)
        DEFINER        - MYSQL_TYPE_STRING  (user@host)
        EVENT_BODY     - MYSQL_TYPE_STRING  (the body from mysql.event)
        EVENT_TYPE     - MYSQL_TYPE_STRING  ("ONE TIME" | "RECURRING")
        EXECUTE_AT     - MYSQL_TYPE_TIMESTAMP (set for "ONE TIME" otherwise NULL)
        INTERVAL_VALUE - MYSQL_TYPE_LONG    (set for RECURRING otherwise NULL)
        INTERVAL_FIELD - MYSQL_TYPE_STRING  (set for RECURRING otherwise NULL)
        SQL_MODE       - MYSQL_TYPE_STRING  (for now NULL)
        STARTS         - MYSQL_TYPE_TIMESTAMP (starts from mysql.event)
        ENDS           - MYSQL_TYPE_TIMESTAMP (ends from mysql.event)
        STATUS         - MYSQL_TYPE_STRING  (ENABLED | DISABLED)
        ON_COMPLETION  - MYSQL_TYPE_STRING  (NOT PRESERVE | PRESERVE)
        CREATED        - MYSQL_TYPE_TIMESTAMP
        LAST_ALTERED   - MYSQL_TYPE_TIMESTAMP
        LAST_EXECUTED  - MYSQL_TYPE_TIMESTAMP
        EVENT_COMMENT  - MYSQL_TYPE_STRING
      
        SQL_MODE is NULL for now, because the value is still not stored in mysql.event .
      Support will be added as a fix for another bug.
      
       This patch also adds SHOW [FULL] EVENTS [FROM db] [LIKE pattern]
      1. SHOW EVENTS shows always only the events on the same user,
         because the PK of mysql.event is (definer, db, name) several 
         users may have event with the same name -> no information disclosure.
      2. SHOW FULL EVENTS - shows the events (in the current db as SHOW EVENTS)
         of all users. The user has to have PROCESS privilege, if not then
         SHOW FULL EVENTS behave like SHOW EVENTS.
      3. If [FROM db] is specified then this db is considered.
      4. Event names can be filtered with LIKE pattern.
        SHOW EVENTS returns table with the following columns, which are subset of
        the data which is returned by SELECT * FROM I_S.EVENTS
         Db
         Name
         Definer 
         Type
         Execute at
         Interval value
         Interval field 
         Starts 
         Ends
         Status
      d847ac54
  17. 23 Jan, 2006 1 commit
  18. 19 Jan, 2006 1 commit
  19. 11 Jan, 2006 1 commit
  20. 16 Dec, 2005 1 commit
    • andrey@lmy004.'s avatar
      WL #1034 update · 5ec6c5f2
      andrey@lmy004. authored
      - varchar -> char
      - transient_expression -> interval_value
      - interval_type -> interval_field
      5ec6c5f2
  21. 15 Dec, 2005 1 commit
    • andrey@lmy004.'s avatar
      WL#1034 update · 533180d7
      andrey@lmy004. authored
      - fix EVENT_ACL problem that GRANT ALL on some_db.* to someone@somewhere did not get to mysql.db
      - fix crash when the following is executed :
        CREATE EVENT P() CREATE EVENT E ON SCHEDULER 1 SECOND DO ROLLBACK;
        (creation works as well as calling P() which creates the event).
      533180d7
  22. 05 Dec, 2005 1 commit
    • andrey@lmy004.'s avatar
      WL#1034 updated · 7120d43c
      andrey@lmy004. authored
      - split into several files
      - forbid parallel execution (before analyse is done how to make it possible)
        because the same sp_head instance cannot be executed in parallel
      - added GPL headers
      - changed EVENT_ACL to be per DB variable
      - fixed minor problems
      7120d43c
  23. 06 Nov, 2005 1 commit
  24. 31 Oct, 2005 1 commit
  25. 13 Oct, 2005 1 commit
    • bar@mysql.com's avatar
      type_binary.result, type_binary.test: · 39b0712c
      bar@mysql.com authored
        new file
      mysql_fix_privilege_tables.sql, mysql_create_system_tables.sh:
        Adding true BINARY/VARBINARY: fixing "password" type, not to be 0x00-padding.
      Many files:
        Adding true BINARY/VARBINARY: fixing tests not to output 0x00 bytes.
        Adding true BINARY/VARBINARY: new pad_char structure member.
      ctype-bin.c:
        Adding true BINARY/VARBINARY: new pad_char structure member.
        New strnxfrm, with two trailing length bytes.
      field.cc:
        Adding true BINARY/VARBINARY.
      39b0712c
  26. 27 Sep, 2005 1 commit
  27. 23 Aug, 2005 1 commit
  28. 27 Jul, 2005 1 commit
  29. 08 Jul, 2005 1 commit
    • pem@mysql.com's avatar
      Fixed BUG#11365: Stored Procedure: Crash on Procedure operation · 5ce9198f
      pem@mysql.com authored
        Two separate problems. A key buffer was too small in sp.cc for multi-byte
        fields, and the creation and fixing of mysql.proc in the scripts hadn't been
        updated with the correct character sets and collations (like the other
        system tables had).
        Note: No special test case, as the use of utf8 for mysql.proc will make
        any existing crash (if the buffer overrrun wasn't fixed).
      5ce9198f
  30. 05 Jul, 2005 1 commit
  31. 17 May, 2005 1 commit
  32. 18 Apr, 2005 1 commit
  33. 16 Apr, 2005 1 commit
  34. 22 Mar, 2005 2 commits