Basilica needs conversation logging.

[Jeremy Thurgood]

Bonus points for being able to import old confbot logs in a useful way.

[Kim van Wyk (kimvanwyk)]

Is there any reason we shouldn't use the old confbot's simple but sufficient db structure, or is there an advantage to adding additional tables or fields?

[Jeremy Thurgood (jerith)]

I think the table structure is probably fine to start with, but we'll have a different username format. Additionally, I want to add better handling for the IRC side and possibly link multiple user identifiers (two different JIDs and an IRC nick, for example) to the same user. All of this would require a certain amount of input data munging, and possibly an extra field if we want to store "message source" and "user" separately.

[Kim van Wyk (kimvanwyk)]

Perhaps then we need 3 tables:
- "messages", with fields:
-- user_id (foreign key on "jid_users" or "irc_users")
-- datetime
-- message

- "jid_users"
-- user_id
-- jid

- "irc_users"
-- user_id
-- irc_nick

The idea being to map all messages to a unique user_id, which the other 2 tables map to one of several JID's or IRC nicks. This is potentially very daft, of course. I can think of 3 drawbacks:
- We lose tracking of which of a users accounts left a given message. This is probably not a biggie hough, as the other users don't care which account Bob used to leave his message
- Perhaps 2 users tables is not necessary and a single "users" table could map user_id to JID/IRC/whatever.
- Perhaps this entire suggestion is really daft and this could be done in a much better fashion.