|Do you know where your variables are?|
I agree with your points against using flat file databases, but in this case those drawbacks will have little effect.
In this case I'm hoping to improve on an existing program that is widely used to create web sites. As such, the schema is unlikely to change radically once defined.
The database will only ever be modified by one person, so there shouldn't be any problems with multiple users writing to the same file. Backups will be made each time a record is modified as described in my reply to MarkM.
Which character to use as a delimiter can be define in a separate configuration file. As the data will be use to create web pages, if the user legitimately needs to use the same character in the text of their page they can use an HTML entity instead.
I agree that a dedicated RDBMS is usually the way to go, but not everyone has the luxury of having access to one (many free hosts still don't offer MySQL).
Text files can be an advantage to this system if one or more of the following applies:-
Storing the data in plain text files is a big advantage in the latter case, as the user has the option to modify the database using a standard text editor.
In reply to Re: Answer: Where is the bottleneck in flat file databases?