[MDEV-5437] DROP TRIGGER command not respecting read_only = 1 setting Created: 2013-12-12 Updated: 2014-11-17 Resolved: 2014-11-16 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Triggers |
| Affects Version/s: | 5.5.34 |
| Fix Version/s: | 5.5.37 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Jonathan Nicol | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | upstream-fixed | ||
| Environment: |
CentOS 5.10 x86_64 |
||
| Description |
|
(also reported to MySQL here: http://bugs.mysql.com/bug.php?id=71136) The "read_only" global variable is not respected by the DROP TRIGGER command, even for a non-SUPER user. It does appear to respect read_only for CREATE TRIGGER. This should return an error, not succeed.
|
| Comments |
| Comment by Savita Agrawal [ 2014-03-07 ] | ||||||||||||||
|
A check (lex->sql_command == SQLCOM_DROP_TRIGGER) in function deny_updates_if_read_only_option() in the file sql_parse.cc does the job! | ||||||||||||||
| Comment by Elena Stepanova [ 2014-11-16 ] | ||||||||||||||
|
The upstream bug is private, but the log and tests suggest that it was fixed in 5.5.37:
The fix was merged into MariaDB 5.5.37. |