SQL Logger

athleticsfan · Post by **athleticsfan** » Mon Aug 21, 2006 4:02 am

Responding to chats is apart of my daily job and I've been looking for a good way to gather data from my chat logs using SQL Logger. The only issue is that it looks like it's a bear to install and I was wondering:

1) Has anyone found any clever shortcuts, like precompiled binaries or other tips and tricks that might help to simplify the installation and setup process?

2) Does it work with the new log format in Adium 1.0b? If not, are there plans to update it soon?

3) Depending on the answer to #1, would someone who's gotten it installed and working well be willing to help me get it working?

Thanks!

Aaron

Post by **The_Tick** » Mon Aug 21, 2006 4:37 am

Answer 1 #1 is no.

Post by **evands** » Mon Aug 21, 2006 5:34 am

2) It is its own logging format and completely separate from anything else related to Adium within the code base.

athleticsfan · Post by **athleticsfan** » Mon Aug 21, 2006 8:43 pm

evands, I'm not sure I understand. I realize that from the point of installation, the logs are being imported into PostgreSQL using a plug-in, but looking at the installation instructions, it looks like you import your existing logs first:

At this point, you're ready to import your logs into the database. Simply use the log_import.pl script, and it will import all of your adium 2.x logfiles.

I guess I was looking for clarification as to what is meant by Adium 2.x logfiles, considering that the release version is at 0.89.1 and the beta is 1.0b9.

Aaron

Post by **bgannin** » Mon Aug 21, 2006 8:57 pm

I believe the issues boil down as so:

- the SQLite Logger plugin hasn't been updated in a while
- references in it refer to the ancient name used by the current incarnation of Adium [that being Adium 2.0, which was later Adium X 0.x and now Adium X 1.0]
- the SQLite Logger, to my knowledge, hasn't been updated to handle the new logging format introduced in Adium 1.0

Post by **evands** » Mon Aug 21, 2006 9:20 pm

Oh, I see, athleticsfan -- I was misunderstanding your question.

The import process has not been modified since the new logging format was created, so, no, as you correctly surmise, it won't currently be able to import your logs.

What I meant was: new logs created by it are not linked to the new logging format, so it will still work as advertised (except the aforementioned import part).