Quote:
My main worry with a database is that a tiny bit of data corruption might wreck the entire save, which wouldn't be such an issue with separate files.
Hmm you have a point with the reliability of a database. It could be a problem if it became corrupted. I'm sure software problems could be handled by good code, and hardware could be resolved by automatic backups. Still it would be nice to only lose part of the data in the event of a crash.
It also seems the possibility of using Tokyo Cabinet is slim to none. It is very linux dependent, and I can't figure out how to get around that fact. No one has developed a port to Windows either.
With this being the case, this BTree organization sounds promising, but I don't really understand how to apply this concept.
Do you mind giving me an overview on how to apply this kind of file saving? I am unsure how to create this kind of file.
Thanks for your help so far!