I just started using Google Chrome and for some reason on certain tasks I get what look like SQL errors? They happen occasionally and if the action is repeated or refreshed usually still work but was wondering what it was?
I have been running Linux Chrome for over a month, and thus far have no more errors than the average user. It might be an individual system glitch, or the combine might not like what you are trying to do.
hmm i haven't seen too many errors lately, it happened a lot around the time i posted the question, it was always DB additions like building where it occurred? possibly timing out somewhere if i remember correctly?
Edited By: Christopher Eagles on Year 11 Day 56 17:49 ____________
"Do not take life too seriously. You will never get out of it alive."
"Every town needs a hero. [walks down a street towards sunset] Every tow
Fatal error: Uncaught exception 'Exception' with message 'UPDATE characters SET shortDescription='', description='Scruffy%20Red%20Hair%2C%20a%20tie%2C%20a%20bright%20yellow%20safety%20jacket%20%26%20a%20Stop%20Sign%20over%20his%20Ailon%20Nova%20Guard%20Uniform', biography='His%20parents etc etc
etc etc etc etc
in /swcombine/http/main/libs/server21/database/DB.inc on line 69
and this one trying to post the above error here -.-
Fatal error: Uncaught exception 'Exception' with message 'UPDATE characters SET postCount=postCount+1 WHERE characterID=1296188 LIMIT 1 caused error: Lock wait timeout exceeded; try restarting transaction' in /swcombine/http/main/libs/server21/database/DB.inc:69 Stack trace: #0 /swcombine/http/main/libs/server21/forum/forum.inc(320): db_query('UPDATE characte...') #1 /swcombine/http/main/www/htdocs/forum/post.php(114): doForumPost('Chrome+and+the+...', 'like+this+one+-...', '39319', Object(Character), NULL, '158', 'reply', '87.114.129.2', false) #2 {main} thrown in /swcombine/http/main/libs/server21/database/DB.inc on line 69
They happen often around daily jobs time and periodically throughout the day. There's nothing you can do about it, and there's not much we can do about it other than systematically trying to make database-intensive activities more efficient, so continuing this sort of discussion is, essentially, mutually pointless.
I haven't noticed anything that the admins didn't say was possabilly going to happen. Then again I'm on the Death Wait and can't see most of the ingame stuff.
In the meantime it's something we'll try and address at the Dev Meeting - to see if we can't do something temporarily to at least decrease the frequency with which they occur.