summaryrefslogtreecommitdiff
path: root/sql/sql_trigger.cc
diff options
context:
space:
mode:
authorunknown <anozdrin@mysql.com>2006-02-13 15:00:01 +0300
committerunknown <anozdrin@mysql.com>2006-02-13 15:00:01 +0300
commit5f1f40233330f5fdce907e83dd87b9fd1cc8a2cd (patch)
tree26fdd47f28f0aa281c442eba15987b776a2f97f4 /sql/sql_trigger.cc
parentdf59e69c03dc72d84a55b107beef93713865a26e (diff)
downloadmariadb-git-5f1f40233330f5fdce907e83dd87b9fd1cc8a2cd.tar.gz
Polishing: after implementing TRIGGER privilege, mysqld option
'--log-bin-trust-function-creators' affects not only replication of the stored functions, but also replication of the triggers. sql/mysqld.cc: Updated the description of mysqld '--log-bin-trust-function-creators' option to reflect that after introducing TRIGGER privilege this option also controls replication of triggers. sql/sql_trigger.cc: Updated the comment to be consistent with the new behaviour, introduced by TRIGGER privilege.
Diffstat (limited to 'sql/sql_trigger.cc')
-rw-r--r--sql/sql_trigger.cc6
1 files changed, 2 insertions, 4 deletions
diff --git a/sql/sql_trigger.cc b/sql/sql_trigger.cc
index 569e5e041c6..0198dba780d 100644
--- a/sql/sql_trigger.cc
+++ b/sql/sql_trigger.cc
@@ -195,10 +195,8 @@ bool mysql_create_or_drop_trigger(THD *thd, TABLE_LIST *tables, bool create)
/*
There is no DETERMINISTIC clause for triggers, so can't check it.
But a trigger can in theory be used to do nasty things (if it supported
- DROP for example) so we do the check for privileges. For now there is
- already a stronger test right above; but when this stronger test will
- be removed, the test below will hold. Because triggers have the same
- nature as functions regarding binlogging: their body is implicitely
+ DROP for example) so we do the check for privileges. Triggers have the
+ same nature as functions regarding binlogging: their body is implicitely
binlogged, so they share the same danger, so trust_function_creators
applies to them too.
*/