Author Topic: Roster and user IDs (Read 4887 times)

Alreadythere · « **Reply #15 on:** May 07, 2008, 10:30:58 pm »

"aotf_online" is theoretical a bug, there should be only one global online table. Of course, all queries using the online table should still use #___online as the name.

prefix_online was an old bug in... 0.4.x or perhaps even 0.3.x.

Nytridr · « **Reply #16 on:** May 07, 2008, 10:53:36 pm »

Quote from: Blueeagle on May 07, 2008, 10:30:23 pm

If the table has first been created you need to drop both *_tablename and the table for it to be recreated properly. It's not enough to change the code to true and then drop the original table as that won't update the *_tablename table.

Also this is not something that's meant to be done as the bot should share the online table.

this is what I did both times, sorry for the miss understanding.

Nytridr · « **Reply #17 on:** May 07, 2008, 10:56:52 pm »

Quote from: Alreadythere on May 07, 2008, 10:30:58 pm

"aotf_online" is theoretical a bug, there should be only one global online table. Of course, all queries using the online table should still use #___online as the name.

prefix_online was an old bug in... 0.4.x or perhaps even 0.3.x.

well since this one is just a relay bot I keep it separate. I do have it in its on db though and not in with the rest of the org bots so it really doesn't matter which way it is to me. but if I were to put it in with the rest of the bots I would like to still keep it separate, but I don't see any reason right now why I would want it that way.
I would not want to do an online on the aotf bot and see everyone on in all the orgs, I would only want to see the bots connected to it.

Alreadythere · « **Reply #18 on:** May 07, 2008, 11:01:13 pm »

The entries of the online table are seperated by the botname setting. Only by explicitely adding other bots in the settings will the online modules use the online information of other bots. No, security wise it's not perfect, but it should be ok enough.