- 31 Jan, 2006 16 commits
-
-
marty@linux.site authored
-
marty@linux.site authored
into linux.site:/home/marty/MySQL/mysql-5.1-new
-
reggie@big_geek. authored
-
reggie@big_geek. authored
into big_geek.:C:/Work/mysql/mysql-5.1
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql51
-
tomas@poseidon.ndb.mysql.com authored
-
reggie@big_geek. authored
-
sasha@asksasha.com authored
into asksasha.com:/reiser-data/mysql-dev/mysql-5.1-new
-
sasha@asksasha.com authored
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new
-
jonas@perch.ndb.mysql.com authored
last bug fix revealed another bug. fix buffer management when parsing table descriptor
-
knielsen@mysql.com authored
into mysql.com:/usr/local/mysql/x/mysql-5.1-new
-
marty@linux.site authored
into linux.site:/home/marty/MySQL/mysql-5.1-new
-
sasha@asksasha.com authored
into asksasha.com:/reiser-data/mysql-dev/mysql-5.1-new
-
sasha@asksasha.com authored
-
tomas@poseidon.ndb.mysql.com authored
+ fix crashing bug when discovering ndb tables outside select context
-
- 30 Jan, 2006 24 commits
-
-
knielsen@mysql.com authored
into mysql.com:/usr/local/mysql/x/mysql-5.1-new
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new
-
jonas@perch.ndb.mysql.com authored
Allow GET_TABINFO during BACKUP (otherwise LCP gets corrupt)
-
reggie@linux.site authored
into linux.site:/home/reggie/work/mysql-5.1
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.1-clean
-
knielsen@mysql.com authored
into mysql.com:/usr/local/mysql/x/mysql-5.1-new
-
knielsen@mysql.com authored
into mysql.com:/usr/local/mysql/x/mysql-5.1-new
-
andrey@lmy004. authored
into lmy004.:/work/mysql-5.1-events_i_s
-
andrey@lmy004. authored
WL#1034 (Internal CRON)
-
reggie@linux.site authored
This bug was fixed through other patches. This test case just shows that it is fixed.
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql51
-
tomas@poseidon.ndb.mysql.com authored
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1
-
knielsen@mysql.com authored
into mysql.com:/usr/local/mysql/mysql-5.1-merge
-
mats@mysql.com authored
into mysql.com:/home/bk/fix-mysql-5.1-new
-
mats@mysql.com authored
when executed using the Perl version of mysql-test-run.
-
knielsen@mysql.com authored
into mysql.com:/usr/local/mysql/mysql-5.1-merge
-
andrey@lmy004. authored
-
knielsen@mysql.com authored
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1
-
svoj@april.(none) authored
into april.(none):/home/svoj/devel/mysql/BUG16722/mysql-5.1-new
-
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
-