The easiest way to make a C1 site permanently fail with no way of automatic recovery is to delete a file from ~/App_Data/Composite/DataStores or even just empty the file or delete a table from database when running in SQL Mode.
This is a complete brain fart since there is NO reason why C1 should be rendered unfunctional because of this. Simply just recreate the file/table. The system has all the necessary information to do it, and if the file is missing, either because of corruption, user error or intentionally there is no way to recover the data anyway and therefor no sane argument for not recreating empty files/tables so the system keep functioning.
I can easily list the first handful discussions on this topic which would never had caused anyone any headaches if this feature had been in place (http://compositec1.codeplex.com/discussions?searchText=hexadecimal%20value%200x00,%20is%20an%20invalid%20character)
Comments: ** Comment from web user: mawtex **
This is a complete brain fart since there is NO reason why C1 should be rendered unfunctional because of this. Simply just recreate the file/table. The system has all the necessary information to do it, and if the file is missing, either because of corruption, user error or intentionally there is no way to recover the data anyway and therefor no sane argument for not recreating empty files/tables so the system keep functioning.
I can easily list the first handful discussions on this topic which would never had caused anyone any headaches if this feature had been in place (http://compositec1.codeplex.com/discussions?searchText=hexadecimal%20value%200x00,%20is%20an%20invalid%20character)
Comments: ** Comment from web user: mawtex **
Judging from the complete lack of reports on this issue on a 4.1 based site it sounds like we finally nailed this issue for XML files. Should an XML file be corrupt on disc we'll keep it, adding the extension .ghost to it so you can salvage data / see what was. And a new file will be created.
If tables "suddenly disappear from the database" the behavior is that the system will start fine (provided this isn't some core table). Trying to access the data type behind this table will lead to an error.