tag:blogger.com,1999:blog-9144505959002328789.post241486260456624319..comments2024-03-28T11:39:50.622+01:00Comments on Karlsson on databases and stuff: More on the MySQL Audit Plugin interfaceKarlssonhttp://www.blogger.com/profile/04874338187076980133noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-9144505959002328789.post-42427864493915932622010-03-28T17:53:23.367+02:002010-03-28T17:53:23.367+02:00Thanx Sergeii. Regarding the parser, you are right...Thanx Sergeii. Regarding the parser, you are right of course that the parser, in terms of sybtax definitions, is in sql_yacc.yy. What sql_parse.cc contains though, is the entry point for the parser itself, i.e. whenever you call "the parser", you actually call a function in sql_parse.cc that in turn calls the parser. But then again, this is not where the auditing is called anyway, so you are probably right.<br /><br />/KarlssonKarlssonhttps://www.blogger.com/profile/04874338187076980133noreply@blogger.comtag:blogger.com,1999:blog-9144505959002328789.post-58135361102429582582010-03-27T08:27:17.067+01:002010-03-27T08:27:17.067+01:00It's a bug, MYSQL_AUDIT_GENERAL_LOG events sho...It's a bug, MYSQL_AUDIT_GENERAL_LOG events should be generated independently from general log being enabled.<br /><br />Besides, there is no source of events inside the <b>parser</b> code. sql_parse.cc is not a parser, sql_yacc.yy is.Anonymousnoreply@blogger.com