An error occurred fetching the project authors.
- 08 Sep, 2017 1 commit
-
-
Eugene Kosov authored
-
- 04 Sep, 2015 1 commit
-
-
Oleksandr Byelkin authored
MDEV-6066: Merge new defaults from 5.6 and 5.7 (defaults changed, QC can be stopped with no-zero size)
-
- 01 Feb, 2006 2 commits
-
-
unknown 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. mysql-test/r/grant.result: Updated the result file after adding TRIGGER privilege. mysql-test/r/information_schema.result: Updated the result file after adding TRIGGER privilege. mysql-test/r/lowercase_table_grant.result: Updated the result file after adding TRIGGER privilege. mysql-test/r/ps.result: Updated the result file after adding TRIGGER privilege. mysql-test/r/sp.result: Updated the result file after adding TRIGGER privilege. mysql-test/r/trigger-compat.result: Updated the result file after adding TRIGGER privilege. mysql-test/r/trigger-grant.result: Updated the result file after adding TRIGGER privilege. mysql-test/t/trigger-compat.test: Grant table-level TRIGGER privilege instead of global SUPER one. mysql-test/t/trigger-grant.test: 1. Grant table-level TRIGGER privilege instead of global SUPER one. 2. Updated the test case to check that SUPER is required to specify the user other than the current as a definer. scripts/mysql_create_system_tables.sh: Added TRIGGER privilege. scripts/mysql_fix_privilege_tables.sql: Added TRIGGER privilege. sql/sql_acl.cc: Added TRIGGER privilege. sql/sql_acl.h: Added TRIGGER privilege. sql/sql_show.cc: Added TRIGGER privilege. sql/sql_trigger.cc: Check TRIGGER privilege instead of SUPER. sql/sql_yacc.yy: Added TRIGGER privilege.
-
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.
-
- 10 Jan, 2006 2 commits
-
-
unknown authored
- fixed test results - fixed bug caught by information_schema.test . Bison temporal variables are very nice but extremely error-prone (Count one more time just to be sure). mysql-test/r/connect.result: fix result for WL#1034 (internal CRON) mysql-test/r/events.result: fix result for WL#1034 (internal CRON) mysql-test/r/grant.result: fix result for WL#1034 (internal CRON) mysql-test/r/information_schema.result: fix result for WL#1034 (internal CRON) mysql-test/r/lowercase_table_grant.result: fix result for WL#1034 (internal CRON) mysql-test/r/ps.result: fix result for WL#1034 (internal CRON) mysql-test/r/system_mysql_db.result: fix result for WL#1034 (internal CRON) mysql-test/t/events.test: fix result for WL#1034 (internal CRON) sql/sql_yacc.yy: - fix bug introduced by me when making usage of temporal bison variables. COUNT 7 times then write!
-
andrey@lmy004. authored
- fixed test results - fixed bug caught by information_schema.test . Bison temporal variables are very nice but extremely error-prone (Count one more time just to be sure).
-
- 18 Feb, 2005 2 commits
-
-
unknown authored
in the grant tables case-insensitive and updating test results. scripts/mysql_create_system_tables.sh: Fix collation of procs_priv.proc_priv scripts/mysql_fix_privilege_tables.sql: Fix enum fields to have case-insensitive collation mysql-test/r/information_schema.result: Update results mysql-test/r/system_mysql_db.result: Update results mysql-test/r/lowercase_table_grant.result: Update results
-
jimw@mysql.com authored
in the grant tables case-insensitive and updating test results.
-
- 15 Feb, 2005 2 commits
-
-
unknown authored
are loaded and lower_case_table_names is set, but issue a warning when it is done. (Bug #7989) sql/sql_acl.cc: Lowercase database names in 'host' and 'db' grant tables when loading, but issue a warning to the log about them.
-
jimw@mysql.com authored
are loaded and lower_case_table_names is set, but issue a warning when it is done. (Bug #7989)
-