An error occurred fetching the project authors.
- 16 Mar, 2006 1 commit
-
-
andrey@lmy004. authored
(one patch)
-
- 10 Mar, 2006 1 commit
-
-
brian@zim.(none) authored
-
- 09 Mar, 2006 1 commit
-
-
cmiller@calliope.local authored
the '-E' or '--events' flag. (Closes Bug#16853 and Bug#17714.) WARNING: At present, these tests fail due to b*g number 18078.
-
- 01 Mar, 2006 3 commits
-
-
andrey@lmy004. authored
WL#1034
-
andrey@lmy004. authored
Events: Event-caused statements don't appear in the slow query log WL#1034
-
andrey@lmy004. authored
Error: Freeing unallocated data at line 900, 'sql_db.cc' ( DROP DATABASE frees thd->db for everything but thd->slave_thread=1 however we are not slave thread and more bugs could appear if we pretend to be, then we will be good boys and just strdup the value. If not DROP DATABASE then THD::~THD() will free the value. )
-
- 28 Feb, 2006 4 commits
-
-
andrey@lmy004. authored
the warnings came from MSFT compiler (output of pushbuild)
-
andrey@lmy004. authored
fix for bug#17793 (Scheduler uses class event_timed should be Event_timed)
-
andrey@lmy004. authored
(post-review pre-push changes) coding style (mostly trailing spaces removed)
-
andrey@lmy004. authored
- now when the event is created and STARTS is omitted then STARTS is implicitly CURRENT_TIMESTAMP - This CS also fixed incorrect presentation of STARTS/ENDS in I_S.EVENTS (incorporated review changes)
-
- 24 Feb, 2006 1 commit
-
-
andrey@lmy004. authored
-
- 21 Feb, 2006 1 commit
-
-
andrey@lmy004. authored
post-review fixes
-
- 20 Feb, 2006 2 commits
-
-
andrey@lmy004. authored
WL#1032 sql_mode setting was disregarded during create/alter event and wasn't set during event execution. (post-review small fixes)
-
andrey@lmy004. authored
WL#1034
-
- 16 Feb, 2006 3 commits
-
-
andrey@lmy004. authored
this problem affects only debug builds
-
andrey@lmy004. authored
| INTERVAL_VALUE | INTERVAL_FIELD | | 20 | 20 MINUTE | the second one should be without the value
-
andrey@lmy004. authored
(pre-push)
-
- 15 Feb, 2006 4 commits
-
-
andrey@lmy004. authored
WL#1034 - This changeset also changes the executor so its quite more stable now. Stressing test case added that executes ~800 events per second and dropping hundreds of events at once using DROP DATABASE. (with fixes after review of JimW) (with fixes after review of Serg)
-
andrey@lmy004. authored
-
andrey@lmy004. authored
-
konstantin@mysql.com authored
-
- 14 Feb, 2006 1 commit
-
-
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)
-
- 10 Feb, 2006 1 commit
-
-
andrey@lmy004. authored
Events were executed with all privileges possible on planet Earth :( WL#1034
-
- 07 Feb, 2006 1 commit
-
-
andrey@lmy004. authored
WL#1034 (Internal CRON) (with post-review fix)
-
- 30 Jan, 2006 3 commits
-
-
andrey@lmy004. authored
WL#1034 (Internal CRON)
-
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
-
knielsen@mysql.com authored
-
- 26 Jan, 2006 2 commits
-
-
andrey@lmy004. authored
(post-review commit) WL#1034 (Internal CRON)
-
andrey@lmy004. authored
WL #1034 (Internal CRON)
-
- 20 Jan, 2006 1 commit
-
-
andrey@lmy004. authored
WL#1034 (Internal CRON)
-
- 18 Jan, 2006 1 commit
-
-
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.
-
- 12 Jan, 2006 1 commit
-
-
andrey@lmy004. authored
- fix compile failure on QNX and FreeBSD
-
- 11 Jan, 2006 1 commit
-
-
andrey@lmy004. authored
after another merge fixes.
-
- 20 Dec, 2005 1 commit
-
-
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.
-
- 16 Dec, 2005 1 commit
-
-
andrey@lmy004. authored
- handle crashes where the table definition has been changed (different number of fields)
-
- 15 Dec, 2005 1 commit
-
-
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).
-
- 13 Dec, 2005 3 commits
-
-
andrey@lmy004. authored
- fixed silly bug, the main thread restarted but did not execute events, Quite currious why many calls to pthread_mutex_init() do not lead to abort()
-
andrey@lmy004. authored
(cleanups, leaks fixed)
-
andrey@lmy004. authored
cleanup before throwin away DYNAMIC_ARRAY for event storage, once reallocated I get dangling pointers so that's not good. solution will be found however ;)
-
- 12 Dec, 2005 1 commit
-
-
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.
-