Re: Database or table level logging?

2006-07-19 Thread Dan Buettner
You might possibly be able to set up a trigger on the log tables to discard entries for all but those databases/tables you are interested in ... Just a thought. Dan On 7/19/06, David Felio <[EMAIL PROTECTED]> wrote: Thanks. I could also get the same result with the existing query log using gr

Re: Database or table level logging?

2006-07-19 Thread David Felio
Thanks. I could also get the same result with the existing query log using grep, but retrieving a little data from a large batch isn't the issue. The issue is the overhead of logging ever single query to the server when I only need a handful of tables. I know we can log everything and retri

Re: Database or table level logging?

2006-07-19 Thread Dan Buettner
Through judicious use of SQL you could easily get the log entries for a specific table ... I haven't got 5.1.6 to check but if the log table included database and table name columns, you're set. select query_text from mysql.general_log where database_name = 'mydb' and table_name = 'mytable' order

Re: Database or table level logging?

2006-07-19 Thread David Felio
Right, sorry, this is 5.0.x (5.0.18 at the moment). Thanks for the pointer on 5.1.6, though that looks like it has the ability to log to a table instead of a file, not log access to a specific table. David On Jul 18, 2006, at 9:23 PM, Chris wrote: David Felio wrote: Is it possible to have

Re: Database or table level logging?

2006-07-18 Thread Chris
David Felio wrote: Is it possible to have general query type logging on just a specific database or table? I don't want all queries to all databases, I just need a log of accesses to a specific table. I figure I can use stored procedures or a separate mysql instance as a workaround if I need to