For those that aren't able to read the german text above:

So what about your problem. Why don't you guys test it? I guess the
database will be faster in the average case, but this also depends on
the database structure for example which indices have to be updated
after an update and of course of the structure you use in the files,
because a database also stores its data into a file ;)
So lets think about an avarage case:
10000 of datarows in the most naive file solution a CSV file. Imaging
you want to alter the 5000th row, you need to load the entire file (at
once or in parts), alter the row and store the whole file. A database
doesn't do so, so it would be of course faster. But if you have say a
B*-Tree structure behind your files you may get the same results a
database get. Well just test it.


Regards
Stefan

Thanks for your answer. We need to write only about 5 lines to the file -
or 1 record to the DB. It's only needed to tell the indexer (of TSEP)
which reads the contents of the files that another instance of the indexer
is already running. So, the first instance started will write to the file
/ db record when it has been started and that it is running at time X
(every 30 seconds)

We will probably favor the simple file.

Sorry, that I missed the english translation of my request and the
explanation what we need this for. Thanks for translating and your comment
Stefan.

Olaf

--
http://www.team-noehring.de

If there is no searching involved, just writing 5 lines (as you specified),
the simple file operation probably is faster. I would be concerned if you're
doing an append and the file size gets rather large, though - you may want
to do a little testing of that scenario.

--
Tony Garcia
Web Right! Development