Phergie_Plugin_Logging port

[elazar]

See http://trac2.assembla.com/phergie/browser/trunk/Phergie/Plugin/Logging.php for the 1.x version of this plugin.

The ported version should be restricted to only logging data to a local database and providing methods for querying that database (including a filter by channel) to other plugins. (i.e. It shouldn't include functionality from the previous Seen, Heard, Willsee, or Search plugins.)

It must include an option to disable logging of message content (such as the bodies of PRIVMSG or NOTICE events) for privacy purposes. Though not necessary, another handy option would be a way to restrict which messages are logged by event type.

[axolx]

elazar -- can you elaborate on what db query methods you were hoping the logging port would implement? i'm also wondering if the responsibility of querying the logs should be left to the plugins that need the data, or to a LogQuery plugin. interested to hear your thoughts, or anyone else's as i work on this port.

[Ttech]

i have a rough design i made in sqlite that was |id|timestamp|channel|who|type|message
and it logs though i cannot imagine my implementation would be the best resources wise

[Ttech]

Well we got a logging module and a logging display site, once it is imported do we need this bug anymore?

[geerlingguy]

Is there any chance something like Seen/Heard will be migrated to the current version of Phergie?