If no disk space remains on the server and txtSQL attempts to update or add a record to a table, then the whole table gets lost.
This happened to me on a university shared server where some other idiot managed to fill the hard disk with log files. I lost all the forum data (I have now learnt to keep backups!) I realise on a properly managed server this wouldn't happen, but unfortunately the IT staff here are hopeless.
Errors I got were firstly a generic php error due to being unable to write session files:
Warning: session_start(): open(/****/sessions/, O_RDWR) failed: No space left on device (28) in /***/auth_check.inc.php on line 4
Followed by the txtSQL error:
txtSQL Warning: Table "ForumTopics" doesn't exist in /****/forum/index.php on line 51
after it had lost the table.
I'm using txtSQL 2.2 Final on php 4. I've temporarily prevented the same thing happening again by disabling the forums when it detects a new file can't be written. Not sure that this is really a 'bug' as such, but its certainly a nuisance if it happens. Has anyone else had this problem?
Thanks for the great script!
Dave
PS Just thought of a possible solution - on update, could txtSQL write the table to a new temporary file e.g. table_tmp and then delete the original and rename if successful?
