[MDEV-4569] TRUNCATE TABLE generates implementation-specific audit events Created: 2013-05-23 Updated: 2013-06-13 Resolved: 2013-06-13 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | 5.5.31 |
| Fix Version/s: | 5.5.32 |
| Type: | Bug | Priority: | Trivial |
| Reporter: | Elena Stepanova | Assignee: | Sergei Golubchik |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | plugins | ||
| Issue Links: |
|
||||||||
| Description |
|
TRUNCATE TABLE is represented by "create" audit event for MyISAM / Aria / MEMORY, and by "write" event for InnoDB. Partial test output:
Test case:
bzr version-info
|
| Comments |
| Comment by Sergei Golubchik [ 2013-06-13 ] |
|
yes, it's unfortunate, but truncate is implemented differently in different engines, and audit events reflect that. |