Annybelly wrote:I guessed other people here who know their techincal stuff *cough* kiwi *cough* would have more idea than a google search could tell me
I realise I'm incredibly late at joining in, but I thought I'd throw in my two cents.
Firstly, clearing the cache
shouldn't have any effect. SQL tables are usually not cached by the browser, because it generally isn't worth it and it could cause all manner of wierdness to occur. Having said that, it is entirely possible that it has happened, and clearing the cache is always a good first step for internet problem solving anyway.
Now onto the more fun stuff. I've seen that error a few times in my server admin days. Basically, SQL is a program that runs on the server that hosts bus, every time you do a search, post something, general browsing, etc, the SQL program reads and writes stuff to a set of tables that hold all the information on the forums. When you want to write something to the tables, the SQL program will buffer it, then push it into the table at a later date (normally quick enough so that you don't notice). If the SQL program crashes before this write has finished, the table may have developed errors. It's the exact same principle as when your computer crashes, sometimes you get inconsistencies and need to run a disk check next time you start up (broadly speaking anyway) to make sure nothing nasty has happened. The SQL program can crash for a whole host of reasons, but usually it is something that has to be reported to the owner/maintainer of the server to investigate further, they'll have to find out why SQL crashed and if it is worth worrying about. I've seen it happen after installing an SQL update, I've also seen it happen just before a catastrophic hardware failure, and sometimes it just crashes randomly.
