Sheeri K. Cabral wrote: > On Wed, Apr 1, 2009 at 2:06 PM, Jeremy Zawodny <[email protected] > <mailto:[email protected]>> wrote:
> > It's very useful to have that option as a sever admin (or someone > who tries to tell them what to do). > > > It's also very useful for forensic purposes. I've used the binary logs > many times to see when lots of data was deleted, or when a table was > dropped. There's no other place to get that kind of information > (unless, heaven save you, you have a general log). > > To that end, I'd like to be able to log all write commands, but perhaps > options like binlog-ignore-db could just comment out the relevant data, > or else have some kind of "no really, log everything" forensic log. In > that case, setting SQL_LOG_BIN=0 should log the commands, but have them > commented out. Well... there's also the logging plugin interface now, with which you could have different logging modules that log different sorts of stuff. Mark's already written one to spit stuff on syslog... could be sensible to write one that spits log entries to gearman or the like. I should mentioned I'm currently working on the road towards being able to do plugins in non-C++ languages. Once that's done, you could write up a quick Python logging module, for instance, that logged exactly what you wanted. Monty _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
