Bug #16597 SUPER needed for triggered tables
| Submitted: | 18 Jan 2006 10:06 | Modified: | 5 Mar 2006 10:19 |
|---|---|---|---|
| Reporter: | Ben Mulder | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server | Severity: | S2 (Serious) |
| Version: | 5.0.18 | OS: | Windows (win-xp) |
| Assigned to: | CPU Architecture: | Any |
[18 Jan 2006 10:06]
Ben Mulder
[18 Jan 2006 13:32]
Aleksey Kishkin
it's documented here: http://dev.mysql.com/doc/refman/5.0/en/create-trigger.html "CREATE TRIGGER was added in MySQL 5.0.2. Currently, its use requires the SUPER privilege."
[5 Mar 2006 10:19]
Konstantin Osipov
This is a duplicate of Bug#9412 (fixed).
[29 May 2007 10:16]
Kris Groves
Any plans to port this fix to 5.0 ?
[6 Aug 2007 13:36]
Constantin Roganov
Please note, that problem applies NOT to CREATE TRIGGER statement, which may require SUPER priv, but to executing a query (INSERT, for example), which throws a trigger. Unfortunately this bug still exists.
[7 Aug 2007 11:21]
Sergei Golubchik
http://dev.mysql.com/doc/refman/5.0/en/create-trigger.html " At trigger activation time, privileges are checked against the DEFINER user. This user must have these privileges: * The SUPER privilege. * The SELECT privilege for the subject table if references to table columns occur via OLD.col_name or NEW.col_name in the trigger definition. * The UPDATE privilege for the subject table if table columns are targets of SET NEW.col_name = value assignments in the trigger definition. * Whatever other privileges normally are required for the statements executed by the trigger. "
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.042 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.