Evaluate a way to store requested informations in a DB
We currently get: Signon, Account if set, Ident, Host, realname, Nick, Idle, Away if set. We need a way to store this information. We can:
- Store each event (e.g. the bot requests the data, and stores idle time, signon etc at that moment)
- Makes the DB a big one
- We have much details, and can go into the deep analysis
- Store the current values
- Makes the DB not so big
- Make us lose a lot of information: e.g. if the user is reconnecting, the old signon will get overriden
We also need a way to store, and a way to query these information. For example a timestamp when the entry was recorded using UNIX would make sense. Next question is:
- Should we store the chans the user is in, and that the bot is in too? Whois can give us that information. But how do we store that? varchar with Strings seperated by comma, or how?