- 02 Feb, 2006 3 commits
-
-
elliot@mysql.com authored
-
elliot@mysql.com authored
into mysql.com:/home/emurphy/src/mysql/bk-clean/mysql-5.1-new-merge
-
stewart@mysql.com authored
-
- 01 Feb, 2006 37 commits
-
-
elliot@mysql.com authored
into mysql.com:/home/emurphy/src/mysql/bk-clean/mysql-5.1-new-merge Null-merge InnoDB snapshots from 5.0 to 5.1
-
dlenev@mysql.com authored
into mysql.com:/home/dlenev/src/mysql-5.1-merges
-
mskold@mysql.com authored
-
mskold@mysql.com authored
into mysql.com:/usr/local/home/marty/MySQL/mysql-5.1-new-wl1892
-
dlenev@mysql.com authored
into mysql.com:/home/dlenev/src/mysql-5.1-merges
-
dlenev@mysql.com authored
into mysql.com:/home/dlenev/src/mysql-5.1-merges
-
konstantin@mysql.com authored
into mysql.com:/home/kostja/mysql/mysql-5.1-merge
-
dlenev@mysql.com authored
When we add new privilege we should update mysql-test/lib/init_db.sql accordingly.
-
pekka@mysql.com authored
into mysql.com:/space/pekka/ndb/version/my51
-
pekka@mysql.com authored
-
konstantin@mysql.com authored
into mysql.com:/home/kostja/mysql/mysql-5.1-merge
-
konstantin@mysql.com authored
into mysql.com:/home/kostja/mysql/mysql-5.1-merge
-
mskold@mysql.com authored
into mysql.com:/usr/local/home/marty/MySQL/mysql-5.1-new-wl1892
-
mskold@mysql.com authored
-
stewart@mysql.com authored
into mysql.com:/home/stewart/Documents/MySQL/5.1/tmp_merge
-
stewart@mysql.com authored
into mysql.com:/home/stewart/Documents/MySQL/5.1/tmp_merge
-
stewart@mysql.com authored
fix up test cases.
-
knielsen@mysql.com authored
into mysql.com:/data0/mysqldev/my/mysql-5.1-new
-
knielsen@mysql.com authored
-
knielsen@mysql.com authored
-
konstantin@mysql.com authored
into mysql.com:/home/kostja/mysql/mysql-5.1-merge
-
tomas@poseidon.ndb.mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql51
-
tomas@poseidon.ndb.mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
corrected test case
-
tomas@poseidon.ndb.mysql.com authored
correction
-
mskold@mysql.com authored
into mysql.com:/usr/local/home/marty/MySQL/mysql-5.1-new-wl1892
-
tomas@poseidon.ndb.mysql.com authored
-
mskold@mysql.com authored
-
mskold@mysql.com authored
-
anozdrin@mysql.com authored
into mysql.com:/mnt/hda4/home/alik/MySQL/devel/5.1-bug9412-latest
-
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.
-
marty@linux.site authored
-
tomas@poseidon.ndb.mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
-
stewart@mysql.com authored
into mysql.com:/home/stewart/Documents/MySQL/5.1/wl1359
-
tomas@poseidon.ndb.mysql.com authored
-