Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#13 2006-03-09 00:38:30
- Mary
- Sock Enthusiast
- Registered: 2004-06-27
- Posts: 6,236
Re: Broken database
Overhead is “leftover mess” when you remove stuff from the database. Corruption is being actually broken because something failed (a process, a harddrive…) in the middle of updating the table, and is not a normal occurence. If it starts to become a problem you need to call your webhost.
colak was talking about overhead in the logs table, not your corrupted article table.
Offline
#14 2006-03-09 03:19:22
- tiger
- New Member
- Registered: 2006-03-06
- Posts: 6
Re: Broken database
I really regret not saving the error messages – this was not a problem with my webhost. This was something that happened when textpattern interacted with the database. I know what overheads are – they don’t stop you reading the table.
Offline
Re: Broken database
Exactly, that’s what zem and mary are saying: overhead has nothing to do with corruption. You had corruption, but other people were suggesting things that related to overhead.
The actual “source” of your problem cannot be textpattern though, because textpattern doesn’t have any low level access to the db, txp – like any other php-based software – uses a very high level library to talk with the db (the mysql-library in PHP), which totally encapsulates all db-stuff into simply things like read/write/run this query etc.. The reason why your table gets coupted lies with the server, not any php-based software.
(If you forgive this analogy: Just like your telephone won’t break, because of the numbers you dial, or the stuff you talk about on the phone)
I remember two specific reasons for recurring corrupted tables: One person was using an alpha version of mysql, that had still many bugs with repsect to full-text indices. Another person has mad many server-lockups and reboots from which either mysql or the filesystem recovered with problems each time.
Offline