Archive > BeBot 0.2 support

Error

<< < (2/2)

Alreadythere:
Most devs are using the SVN version I think, and no longer 0.2.x.

So the chances of anything in the 0.2 branch getting fixed fast aren't the best.

That said - I don't know if moving to 0.3.5+ would solve the problem. Though I got no trouble using the items command in my bots.

Aesgaard:
I'll try upgrading, if not mistaken I need to redo the entire mysql db or delete it and build a new one for the 0.3+ build ? or would you reccomend waiting for 0.4 as Khalem said would probably be released this weekend ?

Alreadythere:
There won't be any major changes till 0.4 anymore, only some error fixing and internal cleanup. Besides, with 0.3.4 we started to include automatic table updates where needed, which means even if some table changes till 0.4 (which is extremely unlikely), it will automatically update the schema on the next startup.

You'll need to redo quite a bit though, yes. Some things can be reused if you know how to rename SQL tables.
Just get a clean copy of 0.3.5 or 0.4 running, and check tables - if they got the same schema you can just reuse them.

Aesgaard:
I better just clear it :P

porter:
By the way, as far as I can tell this was an anomaly, what I saw in the logs before and soon after the incident is extremely quick responses to any !items queries. We are also not even in the same country, Aesgaard and I, so the same timeout issue hitting us both would seem to indicate a problem somewhere closer to the items database server. Regardless, similar might of course happen again with the way this particular module queries the external database. I'm too busy IRL to upgrade right now but I also do not see it as a major problem currently.

Navigation

[0] Message Index

[*] Previous page