An error occurred fetching the project authors.
  1. 29 May, 2006 1 commit
  2. 22 May, 2006 1 commit
    • andrey@lmy004.'s avatar
      fix for bug #17619 Scheduler race conditions · b429d73d
      andrey@lmy004. authored
      - Scheduler is either initialized at server start or never.
        Starting & stopping is now suspending & resuming.
      - The scheduler has clear OO interface
      - Now all calls to the scheduler are synchronous
      - GLOBAL event_scheduler uses thd::sys_var_tmp (see set_var.cc)
      - External API is encapsulated into class Events
      - Includes fixes for all comments of Kostja's review of 19.05.2005
      
      Starting to merge into 5.1-release (5.1.10) and push
      b429d73d
  3. 16 Mar, 2006 1 commit
  4. 28 Feb, 2006 2 commits
  5. 20 Feb, 2006 2 commits
  6. 16 Feb, 2006 1 commit
  7. 15 Feb, 2006 2 commits
  8. 14 Feb, 2006 1 commit
    • andrey@lmy004.'s avatar
      - final fixes for bug#16431 (Events: An event which alters itself disappears) · 815927e5
      andrey@lmy004. authored
      - fix for bug#16423 (Events: SHOW CREATE EVENT doesn't work)
      - this Changeset commits makes CREATE/UPDATE/DELETE EVENT real DDL statements
        by committing the currently open transaction before they are executed.
      - this Changeset also fixes a trailing space problem since the very early days
        of the internal cron
      - adds sophisticated checking of whether mysql.event was tampered accidentally
        or with purpose by an user.
      - adds a lot of inline function documentation - documents everything left
        uncodumented
      - INTERVAL_XXXX to XXX in I_S.EVENTS.INTERVAL_FIELD
      
      WL#1034 (Internal CRON)
      815927e5
  9. 10 Feb, 2006 1 commit
  10. 31 Jan, 2006 1 commit
  11. 30 Jan, 2006 2 commits
    • 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
    • knielsen@mysql.com's avatar
  12. 18 Jan, 2006 1 commit
    • andrey@lmy004.'s avatar
      - fix bug #16435 (Weekly events execute every second) (WL#1034 Internal CRON) · 0322cb1d
      andrey@lmy004. authored
      Before the interval expression was considered to be in seconds, now it is
      just a number and the type of interval is considered.
      
      - this changeset introduces also fix for bug#16432 (Events: error re interval
        misrepresents the facts)
        the code of event_timed::set_interval() was refactored anyway so it is meaningful to
        fix the bug in the same changeset.
      0322cb1d
  13. 12 Jan, 2006 2 commits
  14. 10 Jan, 2006 1 commit
  15. 28 Dec, 2005 1 commit
    • andrey@lmy004.'s avatar
      WL #1034 (update) · b95f342f
      andrey@lmy004. authored
      - improve the stability of the executor
      - make create event if not exists work as before
      b95f342f
  16. 20 Dec, 2005 1 commit
    • andrey@lmy004.'s avatar
      WL #1034 update · fa9f2a77
      andrey@lmy004. authored
      - fix one bug found by PeterG, namely bug #51
      
      #there is a major problem currently after removing the specialised DYNAMIC_ARRAY as 
        storage for the events. I have to reintroduce similar storage, this time probably some
        linked list or maybe some API on top of DYNAMIC_ARRAY.
      fa9f2a77
  17. 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
  18. 12 Dec, 2005 1 commit
    • andrey@lmy004.'s avatar
      WL#1034 update · d94bae3a
      andrey@lmy004. authored
      QUEUE implementation working now. this should be ready more or less
      for testing once the debug output is being cleaned and some things
      around DYNAMIC_ARRAY are cleaned
      - fix handling in case of errors that lead to crashes, now no more crashes
        in case of table corruption and such.
      d94bae3a
  19. 08 Dec, 2005 1 commit
  20. 07 Dec, 2005 2 commits
  21. 06 Dec, 2005 1 commit
  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. 02 Dec, 2005 1 commit