Details
Description
When an warnings is converted into an error because of the strict sql_mode, this conversion happens inside THD::raise_condition. And my_message_sql is not called, so no audit events are generated for this error.
Possible fixes:
- generate audit events from THD::raise_condition (then they won't be generated when thd == 0)
- always invoke my_message_sql for every error
- some other way to make sure that all error processing code is invoked for any error
Gliffy Diagrams
Attachments
Issue Links
- relates to
-
MDEV-4846 SQL_ERROR_LOG plugin doesn't log errors produced with SIGNAL
-
- Closed
-
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Proposed fix:
http://lists.askmonty.org/pipermail/commits/2013-December/005777.html
Also fixes the mentioned
MDEV-4846.