An error occurred fetching the project authors.
- 21 Nov, 2006 1 commit
-
-
gkodinov/kgeorge@macbook.gmz authored
- TRUNCATE requires DROP privilege, not DELETE
-
- 01 Jun, 2006 1 commit
-
-
mats@mysql.com authored
Under row-based replication, DELETE FROM will now always be replicated as individual row deletions, while TRUNCATE TABLE will always be replicated as a statement.
-
- 18 May, 2006 1 commit
-
-
knielsen@mysql.com authored
-
- 12 May, 2006 1 commit
-
-
kroki@mysql.com authored
from within triggers Add support for passing NEW.x as INOUT and OUT parameters to stored procedures. Passing NEW.x as INOUT parameter requires SELECT and UPDATE privileges on that column, and passing it as OUT parameter requires only UPDATE privilege.
-
- 09 Mar, 2006 1 commit
-
-
anozdrin@mysql.com authored
-
- 06 Feb, 2006 1 commit
-
-
anozdrin@mysql.com authored
-
- 01 Feb, 2006 1 commit
-
-
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.
-
- 24 Jan, 2006 1 commit
-
-
anozdrin@mysql.com authored
- BUG#15166: Wrong update permissions required to execute triggers - BUG#15196: Wrong select permission required to execute triggers The idea of the fix is to check necessary privileges in Item_trigger_field::fix_fields(), instead of having "special variables" technique. To achieve this, we should pass to an Item_trigger_field instance a flag, which will indicate the usage/access type of this trigger variable.
-
- 12 Jan, 2006 1 commit
-
-
anozdrin@mysql.com authored
-
- 10 Nov, 2005 1 commit
-
-
anozdrin@mysql.com authored
checks on trigger activation)
-